Suspicious Startup Persistence via Registry Run Key Pointing to Script

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

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 a registry Run key value being set to a VBScript or JScript file, a startup persistence method used by Pure Crypter alongside scheduled tasks. Run keys that launch script files at logon are a frequent malware persistence mechanism and should be validated against known good software.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Run Key Persistence Masquerading as MicrosoftUpdate via Axios npm Compromise
Suspicious User Shell Folders Startup Redirect for Persistence via Registry
Malicious XRed Backdoor Execution from ProgramData Synaptics Path (via process_creation)
Suspicious Double Extension Executable Execution via Command Line
Suspicious SCMBanker Autostart Persistence via Run Key VBScript
Malicious Run Key Persistence Pointing to Renamed PowerShell via Axios Compromise
Suspicious PowerShell Persistence via Registry Run Key
Possible SHELBY Backdoor Persistence via Run Key Referencing AppData HTTPApi
Suspicious Run Key Persistence Pointing to Test Executable via Registry Set
Suspicious Startup Persistence via Registry Run Key Pointing to Script
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.