Windows Registry: Wow6432Node NT CurrentVersion Autorun Keys Modification

Alerts on registry modifications to Wow6432Node NT CurrentVersion autorun-related keys tied to persistence behavior.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Victor Sergeev, Daniil Yugoslavskiy, Gleb Sukhodolskiy, Timur Zinniatullin, oscd.community, Tim Shelton, frack113 (split) (SigmaHQ), DRL 1.1
Published
2019-10-25
Updated
2026-07-30

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 flags registry writes targeting the 32-bit compatibility hive under SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion and specifically keys associated with autostart extensibility. Such changes can enable persistence by redirecting or loading attacker-controlled components at startup or process execution time. It relies on registry_set telemetry that includes TargetObject and Details fields, while excluding empty and null Details values and filtering out entries ending with the Image File Execution Options path.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious Run Key Persistence Referencing DLL in User Documents
PlugX Persistence via Run Key Named AAM Updatevlm
Suspicious Autorun Registry Persistence via sausageLoop Run Key
Malicious BabyLockerKZ Run Key Persistence
Suspicious Run Key Persistence Pointing To User-Writable Path
Malicious Ctrlpanel Run Key Autostart Persistence (via registry_set)
Persistence Run Key Pointing to svchost.exe in AppData Roaming
URL Shortcut File Created in Startup Folder for Persistence
Suspicious Run Key Persistence via UpdateCheck Value in Operation TrueChaos
Windows Registry: Wow6432Node NT CurrentVersion Autorun Keys Modification
Pivot detection · T1547.001 · 9 related

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