Suspicious SCMBanker Autostart Persistence via Run Key VBScript

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

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 Run or RunOnce autostart entry pointing at a run.vbs script which SCMBanker establishes for persistence after initial compromise. The banking-fraud toolkit relaunches its VBScript loader at logon to survive reboots. A user-hive autostart referencing a loose VBScript is a reliable persistence signal.

Related detections9 linkedT1547.001 — drag to rearrange
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
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
Suspicious Wscript Spawning Embedded Python Interpreter (via process_creation)
Suspicious SCMBanker Autostart Persistence via Run Key VBScript
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.