Possible WSHRAT Persistence via Run Key Silent Script Execution

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-02
Updated
2026-11-02

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 Registry Run key value being set to launch wscript with the batch //B flag against a VBScript file. WSHRAT establishes persistence by writing an HKCU Run entry that silently executes its dropped .vbs payload at logon. This ensures the RAT survives reboots while running without a visible window.

Related detections9 linkedT1059.005 — drag to rearrange
Suspicious VBScript Persistence in CurrentVersion Run Key
Suspicious SCMBanker Autostart Persistence via Run Key VBScript
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 WarzoneRAT Script Execution from Excel via Windows Script Host
Suspicious Startup Folder LNK Persistence Creation via File System (via file_event)
Suspicious XWorm Persistence Run Key Pointing to Batch Loader via ScreenConnect Lure (via registry_set)
Possible WSHRAT Persistence via Run Key Silent Script Execution
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.