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 linkedT1059.005 — drag to rearrange
Possible WSHRAT Persistence via Run Key Silent Script Execution
Suspicious VBScript Persistence in CurrentVersion Run Key
Suspicious Run Key Persistence via Reg Add
Suspicious Cscript Execution From Alternate Data Stream
Suspicious Run Key Persistence Pointing to ProgramData Executable
Malicious Run Key Persistence via wininfo64 Path by Italian Infostealer (via registry_set)
Suspicious WScript Execution of VBScript From Public Directory
Malicious IcedID Loader Execution via Rundll32 from Excel Macro (via process_creation)
Suspicious Silent VBScript Execution from AppData Roaming
Suspicious SCMBanker Autostart Persistence via Run Key VBScript
Pivot detection · T1059.005 · 9 related

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