Windows Registry Autorun/ASEP Key Modification for Persistence

Alerts on registry modifications to common Windows autorun and persistence extensibility keys indicative of auto-start behavior.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Victor Sergeev, Daniil Yugoslavskiy, Gleb Sukhodolskiy, Timur Zinniatullin, oscd.community, Tim Shelton, frack113 (split), wagga (name) (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 or changes to common Windows autostart extensibility and persistence locations by matching specific registry paths in the TargetObject field. Attackers commonly use these autorun and extensibility points to execute code automatically after logon, disconnect/connect events, or via protocol and script hooks. It relies on Windows registry set telemetry (category: registry_set) and path-based matching, with exclusions intended to reduce noise from known legitimate components and install-time activity.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious WmRAT Persistence via vcswin Run Key (via registry_set)
Malicious PlugX Persistence via LMIGuardian Update Run Key (via registry_set)
Malicious axios NPM Supply Chain Persistence via MicrosoftUpdate Run Key
Malicious Registry Run Key Persistence Masquerading as MicrosoftUpdate
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
Windows Registry Autorun/ASEP Key Modification for Persistence
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.