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 SimpleHelp Remote Access Tool Dropped In ProgramData Root
Suspicious MeshAgent Installation Arguments (via process_creation)
Possible AnyDesk Execution from Non-Standard Directory (via process_creation)
Suspicious MeshAgent Spawning Command Interpreter (via process_creation)
Suspicious AnyDesk Execution from Temporary or System Directory (via process_creation)
Suspicious AnyDesk Unattended Access Password Set via Command Line (via process_creation)
Suspicious PowerShell Spawned by Komari Monitoring Agent
Malicious Command Shell Spawned by Bomgar Remote Support Client
Suspicious Winpty Agent Spawned by Net Monitor Employee Monitoring Process
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.