Suspicious PowerShell Persistence via Registry Run Key

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

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 of a Run key value that launches PowerShell at user logon, matching the RegistryPersistence Beacon Object File demonstrated in Elastic testing of Cobalt Strike detection gaps. Adversaries write a PowerShell payload to the CurrentVersion Run key so their implant re-executes on every startup. A Run entry that invokes PowerShell is a common autostart persistence pattern worth reviewing.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Run Key Persistence via Reg Add
Suspicious Run Key Persistence Pointing to ProgramData Executable
Possible WSHRAT Persistence via Run Key Silent Script Execution
Malicious Run Key Persistence via wininfo64 Path by Italian Infostealer (via registry_set)
Suspicious Startup Folder LNK Persistence Creation via File System (via file_event)
Suspicious XWorm Persistence Run Key Pointing to Batch Loader via ScreenConnect Lure (via registry_set)
Suspicious Run Key Persistence Named AppResolver (via registry_set)
Suspicious SystemBC Persistence via Run Key to ProgramData Script
Suspicious Interlock RAT Persistence via HKCU Run Key Registration to AppData Payload (via process_creation)
Suspicious PowerShell Persistence via Registry Run Key
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.