Suspicious MeshCentral Remote Command Execution via meshctrl (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-08-17
Updated
2026-08-28

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 the MeshCentral meshctrl controller invoking RunCommand, the mechanism ShinyHunters used to push a fanout shell script to compromised PeopleSoft hosts in the education sector campaign. Adversaries abuse remote management platforms like MeshCentral to execute commands at scale across an estate, so controller-driven command execution should be validated against authorized administration.

Related detections9 linkedT1219 — drag to rearrange
Suspicious MeshAgent Persistence via Scheduled Task MeshUserTask (via process_creation)
Suspicious BeyondTrust Bomgar Process Spawning Remote Access Client (via process_creation)
Suspicious RustDesk Remote Access Service Installation via sc (via process_creation)
Suspicious PowerShell Spawned by VBScript for RMM Delivery
Suspicious Silent Installation of Remote Management Software (via process_creation)
MuddyWater NetBird Deployment via Hardcoded Setup Key (via process_creation)
Suspicious Trojanized ScreenConnect Client Installer with Guest Relay Parameters (via process_creation)
Suspicious Remote Utilities RuRAT Host Deployment via Fake Crypto Wallet Installer (via process_creation)
SplashTop Network
Suspicious MeshCentral Remote Command Execution via meshctrl (via process_creation)
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.