Suspicious Run Key Persistence Referencing PowerShell Script via registry_set

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

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects a CurrentVersion Run or RunOnce registry value whose data references a .ps1 PowerShell script, the persistence used in the GST-phishing campaign to relaunch the Remcos RAT loader at logon. A Run key pointing at a script rather than a signed executable is an atypical auto-start that lets the multi-stage .NET chain re-establish itself, so catching the registry write exposes persistence early.

Related detections9 linkedT1059.001 — drag to rearrange
Windows Registry Set in Shell Open Command Using PowerShell Cryptography .NET Classes
Suspicious Hidden PowerShell Spawned by Script Host via process_creation
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Persistence via Windows Update Service Run Key (via registry_set)
Malicious FIN7 Powertrash Loader Execution via Obfuscated PowerShell (via process_creation)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Run Key Persistence Named NvidiaDriverUpdate (via registry_set)
Suspicious XOR Obfuscated PowerShell from ClickFix Distribution
Suspicious Hidden PowerShell Web Download via ClickFix Tactic
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Pivot detection · T1059.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.