Malicious MeshCentral Agent Installation With Campaign Naming

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-05
Updated
2026-10-05

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 detects execution of MeshCentral remote-management agents using the azure-ops and v2 naming observed in ShinyHunters intrusions following the PeopleSoft zero-day exploitation. These specific agent file names are meaningful campaign constants used to blend the remote-access tool into cloud-looking traffic. Their execution indicates attacker-controlled remote management for persistence and lateral movement.

Related detections9 linkedT1219 — drag to rearrange
Suspicious Remote Access Tunneling Tooling on Linux Host
Malicious AnyDesk Unattended Silent Install and Password Set for Remote Access (via process_creation)
Suspicious Cloudflared Tunnel Persistence Installed via msiexec (via process_creation)
Suspicious AnyDesk Silent Install With Unattended Password
Suspicious AnyDesk Unattended Access Configuration via Command Line (via process_creation)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Atera Agent Silent Onboarding via Process Creation
Suspicious Remote Access Tool User Agent in Outbound Traffic via Proxy
Suspicious ScreenConnect Remote Access Binary Running Under a Renamed Executable
Malicious MeshCentral Agent Installation With Campaign Naming
Pivot detection · T1219 · 9 related

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