Suspicious RMM Daisy-Chain Action1 Spawning ScreenConnect via process_creation

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-08-15
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 Action1 RMM agent spawning a ScreenConnect client process. Threat actors daisy-chain remote management tools by using one deployed RMM to install and launch a second, giving them redundant remote access, so an Action1 process launching ScreenConnect indicates chained rogue RMM deployment rather than normal single-vendor management.

Related detections9 linkedT1219 — drag to rearrange
Suspicious ScreenConnect Remote Access Binary Running Under a Renamed Executable
Malicious Silent AteraAgent RMM Installation via IntegratorLogin
Possible Remote Monitoring and Management Tool Abuse for Remote Access
Suspicious NetSupport Manager Client Executing From ProgramData via Process Creation (via process_creation)
Malicious PowerShell Download Cradle Spawned by Quick Assist
Suspicious AnyDesk Unattended Password Set via Piped Echo
Suspicious Remote Monitoring Tool Executing from GoAnywhere Directory
Suspicious NetSupport Manager Remote Client Execution (via process_creation)
Suspicious ScreenConnect Remote Access Client Spawning PowerShell (via process_creation)
Suspicious RMM Daisy-Chain Action1 Spawning ScreenConnect 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.