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
Possible SHELBY Backdoor Persistence via Run Key Referencing AppData HTTPApi
Suspicious Run Key Persistence Pointing to Test Executable via Registry Set
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
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.