Suspicious VBScript Payload Stored in CurrentVersion Registry Value (via registry_set)

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

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Priv Esc

  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 registry values written under HKCU or HKLM CurrentVersion that contain VBScript execution keywords such as Execute, vbscript or Shell.Application. Actors including Nobelium stash script payloads in non-Run CurrentVersion values to hide fileless persistence outside the commonly scrutinized Run subkeys.

Related detections9 linkedT1112 — drag to rearrange
PowerShell VBScript RegWrite Registry Modification Attempts
VBScript Registry Write Attempt via Wscript.shell RegWrite on Windows
Suspicious Script Host Spawning LOLBins Used by XWorm Loader (via process_creation)
Suspicious Remote Desktop Disable via fDenyTSConnections Registry Modification (via registry_set)
Suspicious Offline Registry Hive Library Loaded from User-Writable Path for Stealth Persistence (via image_load)
GuLoader VBScript Execution from Music BUG Staging Directory (via process_creation)
Suspicious Autostart Persistence via Registry Run Key Pointing to a Script Interpreter (via registry_set)
Masquerading PNGPlug Loader Payload Path Storage via DICKEXEPATH Registry Value (via registry_set)
IMEEX Framework Configuration Persistence via IMEEX Registry Subkeys (via registry_set)
Suspicious VBScript Payload Stored in CurrentVersion Registry Value (via registry_set)
Pivot detection · T1112 · 9 related

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