Suspicious Autostart Persistence via Run Key Pointing Outside Program Files (via registry_set)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

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 a Run or RunOnce registry value whose data points to an executable outside the Program Files directories, a persistence-hunting heuristic from Group-IB Hunting Rituals. Adversaries register autostart entries that launch payloads from user-writable locations to survive reboot, so Run values referencing non-standard paths warrant review.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Run Key Persistence With Masqueraded System Binary by Millenium RAT (via registry_set)
Suspicious RunOnce Persistence Relaunching Payload with Safe Mode Flag
Suspicious DarkMe Cabinet.ocx Payload Dropped in AppData WinSoft Directory
Suspicious Run Key Persistence Executing regsvr32
Suspicious Ousaban Persistence via Financeiro Run Registry Value (via registry_set)
Suspicious Winos Persistence Binary Created as ProgramData BITTS2.exe (via process_creation)
Suspicious Ousaban Installation Marker maisum.dat Created (via file_event)
Suspicious Shahmaran Autostart Masquerading as Adobe Updater
Suspicious K7Soft Autostart Persistence
Suspicious Autostart Persistence via Run Key Pointing Outside Program Files (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.