macOS Process Creation: MeshAgent Remote Access via --meshServiceName

Alerts on macOS process executions containing --meshServiceName, indicating potential MeshAgent remote access usage.

FreeReviewedSigma · Medium · 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

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule flags macOS process creations whose command line contains the "--meshServiceName" argument, indicating potential MeshAgent remote access usage. Remote access tooling is commonly abused by attackers for persistence and command-and-control, and attackers may rename MeshAgent binaries to reduce detection. The detection relies on macOS process creation telemetry and the presence of the specific command-line argument.

Related detections9 linkedT1219 — drag to rearrange
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
Windows MeshAgent Remote Access Tool Command Line Execution Indicators
Windows Process Creation: Microsoft QuickAssist.exe Execution
Windows MeshAgent remote command execution via cmd.exe or PowerShell child processes
Windows Incoming AnyDesk Connection via AnyDesk.exe or AnyDeskMSI.exe
Windows File Drop Indicators for RemoteKrbRelay SMB Relay Secret Dump Module
Windows DNS Queries to azurewebsites.net From Non-Browser Processes
Windows CSharp Streamer RAT Potentially Loaded .NET Executable from Temp dat####.tmp
Windows SimpleService Execution via Remote Access Tool Wrapper Paths
macOS Process Creation: MeshAgent Remote Access 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.