Suspicious VBScript Execution from Public User Directory (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-21
Updated
2026-09-21

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects Windows Script Host running a VBScript dropped into the C\Users\Public directory, matching the tax-themed GuLoader chain where a .lnk uses PowerShell to save Fjoua.vbs to Public before execution. The Public folder is an atypical location for legitimate scripts and is chosen to evade per-user monitoring. This stages GuLoader to deliver the Remcos RAT.

Related detections9 linkedT1204.002 — drag to rearrange
Malicious LitterDrifter VBScript Execution via wscript trash.dll
Suspicious WScript Execution Spawned by Microsoft Word (via process_creation)
Uncommon Kimsuky OneNote Document Spawning Script Interpreter (via process_creation)
Malicious Excel Macro Spawning Scripting Interpreter Downloader (via process_creation)
Windows AppLocker Audit-Mode Events Indicate Files Would Have Been Blocked
Windows AppLocker Blocked Application, Script, MSI, or Packaged-App Execution
Suspicious Double-Extension PDF JavaScript Lure via WScript (via process_creation)
Suspicious Encoded JScript Execution via WScript (via process_creation)
Suspicious AutoIt3 Executing Script from User Writable Path via Command Line
Suspicious VBScript Execution from Public User Directory (via process_creation)
Pivot detection · T1204.002 · 9 related

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