Windows: Abused Debug Privilege via Command-Line Route/Add Spawned by System Parents

Flags PowerShell/cmd spawned by system processes with command lines containing both 'route' and 'ADD'.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Semanur Guneysu @semanurtg, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-28
Updated
2026-07-30

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies suspicious child processes (PowerShell or cmd) spawned by common Windows system processes under specific user name patterns. It matters because attackers may leverage these high-trust parent contexts to establish execution paths associated with privilege escalation attempts. The detection relies on Windows process creation telemetry, matching parent image endings, child image/original file name indicators, and command-line content containing both 'route' and 'ADD'.

Related detections9 linkedT1548 — drag to rearrange
Malicious Sapphire Sleet TCC Privacy Database Tampering via sqlite3 (via process_creation)
Suspicious storagekitd Spawning Third-Party Filesystem Binary from Library Filesystems (via process_creation)
Malicious Switch User to Rogue Root-Equivalent Account troot (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Possible GTFOBins Shell Breakout via Unix Utilities
Malicious Azure Elevate Access to User Access Administrator
Suspicious User Home Directory Modification via dscl Process Creation
Possible GTFOBins Shell Breakout via apt Command
Malicious Update Orchestrator Service Reconfiguration for Privilege Escalation
Windows: Abused Debug Privilege via Command-Line Route/Add Spawned by System Parents
Pivot detection · T1548 · 9 related

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