PowerShell Storing an Encoded Payload in the Registry (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-03
Updated
2026-09-03

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects PowerShell writing a base64 or byte-array value into an HKCU registry key, the fileless persistence and staging behavior seen in Solarmarker and Yellow Cockatoo intrusions. Storing an encoded payload in the registry is a defense-evasion and persistence technique tracked in the Red Canary Threat Detection Report. Detecting this write surfaces a fileless payload being cached for later execution.

Related detections9 linkedT1112 — drag to rearrange
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Suspicious Access to Chrome Encrypted Preference MAC Registry Values (via registry_set)
Suspicious Flax Typhoon Network Level Authentication Disabled via Registry (via registry_set)
Suspicious Deletion of Terminal Server Client History via reg by UNC1549
Suspicious Registry Class Key Creation for COLDRIVER Persistence
Suspicious Modification of CloudFiles BlockedApps Policy via registry_set
PowerShell Storing an Encoded Payload in the Registry (via process_creation)
Pivot detection · T1112 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.