macOS Process Creation: MeshAgent renamed execution via --meshServiceName

Identifies macOS executions of MeshAgent instances that include --meshServiceName, indicating potential renamed remote access tooling.

FreeReviewedSigma · High · v2
Product
macos
Category
process_creation
Author
Norbert Jaśniewicz (AlphaSOC) (SigmaHQ), DRL 1.1
Published
2025-05-19
Updated
2026-07-31

ATT&CK techniques

Defense Evasion → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule flags macOS process creation events where the command line contains the MeshAgent-specific parameter "--meshServiceName" while the process appears to be a renamed instance of MeshAgent. Attackers may rename RMM tooling to evade allowlists and simple detections, which can enable persistent remote control. The detection relies on process_creation telemetry, matching the command-line argument and excluding known legitimate MeshAgent paths via image filename endings.

Related detections9 linkedT1036.003 — drag to rearrange
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
Suspicious Renamed Tunneling Tool Executing from Windows Tasks Directory
Suspicious AnyDesk Unattended Access Configuration via Command Line (via process_creation)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Renamed PowerShell Binary Execution (via process_creation)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious Renamed PowerShell Copied from System32 via Batch Loader
Suspicious Atera Agent Silent Onboarding via Process Creation
Suspicious Remote Access Tool User Agent in Outbound Traffic via Proxy
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Pivot detection · T1036.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.