Suspicious Command Processor AutoRun Persistence via Registry Set

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-05-14
Updated
2026-08-28

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects writes to the Command Processor AutoRun registry value, which forces a command to run whenever cmd.exe starts and was used for persistence in the Uncorking Old Wine Cobalt Strike loader. This value is rarely set by legitimate software and is a well-known event-triggered execution vector.

Related detections9 linkedT1546 — drag to rearrange
Suspicious Python Path Configuration Hook Persistence (via file_event)
Suspicious Zsh Persistence via zshrc_aliases Appended to Shell Startup (via process_creation)
Malicious UNC4841 Dropper Deployment to Boot Partition via mknod (via process_creation)
Suspicious Image File Execution Options Debugger Set to ntsd
Suspicious Image File Execution Options Debugger Hijack
Suspicious NetworkManager Dispatcher Script Persistence
Suspicious APT Or YUM Package Manager Hook Configuration Created
Suspicious Image File Execution Options Debugger Hijack (via registry_set)
Malicious IFEO Debugger Hijack of vds.exe by FishMonger
Suspicious Command Processor AutoRun Persistence via Registry Set
Pivot detection · T1546 · 9 related

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