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 linkedT1219 — drag to rearrange
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
Suspicious n8n Campaign RMM Installer Masquerading as OneDrive Document
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Malicious Scheduled Task Masquerading as GoogleUpdate Launching SSH Reverse Shell
Malicious NetSupport RAT Client32 Execution
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
Suspicious Outbound Connection To MoonPeak C2 High Ports
Suspicious Remote Management C2 Subdomain Resolution
Suspicious MeshAgent Persistence via Scheduled Task MeshUserTask (via process_creation)
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Pivot detection · T1219 · 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.