Suspicious Run Key Persistence in CurrentVersion (via registry_set)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-05
Updated
2026-10-05

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 creation or modification of ASEP Run key values under HKLM or HKCU CurrentVersion that point to executables in user-writable or temporary directories. DragonForce establishes autostart persistence via Run keys so its loader relaunches on logon, maintaining foothold through reboots.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious Sibot Malware Registry Persistence Value
Suspicious Run Key Persistence Referencing Script Files Linked to FIN7
Suspicious LNK Persistence Dropped in Startup Folder
Suspicious LNK File Created In Startup Folder For Persistence
Suspicious OCEANMAP EdgeContext.url Startup Persistence (via file_event)
Suspicious PIF Persistence File in Public Libraries (via file_event)
Suspicious GhostSocks Run Key Persistence to AppData Cache via registry_set
Suspicious Run Key Persistence Masquerading as NVIDIA Driver Update
Suspicious Run Key Persistence Executing system.bat via registry_set
Suspicious Run Key Persistence in CurrentVersion (via registry_set)
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.