Windows WMIC loading JavaScript/VBScript engine libraries

Alerts on wmic.exe loading jscript.dll or vbscript.dll, a common sign of script execution via Windows Management Instrumentation.

FreeReviewedSigma · Medium · v2
Product
windows
Category
image_load
Author
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research) (SigmaHQ), DRL 1.1
Published
2020-10-17
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows processes that load wmic.exe and subsequently load the scripting runtime libraries jscript.dll or vbscript.dll. Such library loading indicates WMIC is being used to execute or proxy scripting functionality, which can help attackers bypass application controls. The detection relies on image load telemetry (the loaded module paths) that associates script engine DLL loads with WMIC execution. Investigate the parent process and command line around the WMIC invocation to confirm intent, as benign WMIC queries can also trigger vbscript.dll loads.

Related detections5 linkedT1220 — drag to rearrange
XSL Script Processing via WMIC or MSXSL (via process_creation)
Suspicious msxsl Execution with Text Script Dropper
Malicious Remote XSL Script Execution via WMIC Squiblytwo Technique
Windows msxsl.exe Execution with HTTP Keyword in Command Line
Windows Msxsl.exe Execution
Windows WMIC loading JavaScript/VBScript engine libraries
Pivot detection · T1220 · 5 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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