WindowsT1059.005

>cscript.exe

CScript.exe is a command-line version of the Windows Script Host that facilitates running VBScript and JScript scripts. Frequently abused to run dropped scripts, execute obfuscated VBScript files, and perform defense evasion.

Default Executable Paths

C:\Windows\System32\cscript.exe
C:\Windows\SysWOW64\cscript.exe

Integrity & Metadata

Original Name: cscript.exe
File Version: 10.0.19041.1
Category Count: 1 weaponized patterns
Forensics & Triage Insight

Check for execution from user-writable directories or scripts pulling data from Alternate Data Streams (ADS).

Detection Engineering Notes

Look for cscript.exe executing scripts from %TEMP%, %APPDATA%, or running with //E:VBScript switches against masqueraded file extensions.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

cscript.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse cscript.exe as a Living-off-the-Land Binary (LOLBin) to achieve Execute without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Execute
Minimum Privilege
User
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1059.005

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:

Runs a VBScript quietly without banner or user alerts from a temporary location.

cscript.exe //B //Nologo %TEMP%\recon.vbs

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (cscript.exe)

Validated against MITRE T1059.005
cscript.exe Microsoft Defender Querykql
1DeviceProcessEvents
2| where FileName in~ ("cscript.exe", "wscript.exe")
3| where ProcessCommandLine has_any ("\\Temp\\", "\\AppData\\", "\\Public\\")
4| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain cscript.exe abuse.

Application Whitelisting

Enforce Windows Defender Application Control (WDAC) or AppLocker publisher rules to prevent execution outside approved enterprise administration scripts.

Attack Surface Reduction

Enable ASR rules: Block executable content from email client and webmail and Block Office applications from creating child processes spawning cscript.exe.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • cscript.exe

Key operational questions and defensive answers about cscript.exe LOLBin tradecraft.

What is cscript.exe and why is it classified as a LOLBin?

cscript.exe is a legitimate, pre-installed or trusted utility on Windows. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Execute—without dropping custom malware binaries on disk.

How do threat actors abuse cscript.exe in cyber intrusions?

Adversaries leverage cscript.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "cscript.exe //B //Nologo %TEMP%\recon.vbs" to achieve Execute, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious cscript.exe activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning cscript.exe), and unexpected network connections.

What MITRE ATT&CK techniques does cscript.exe map to?

cscript.exe maps to MITRE ATT&CK technique(s): T1059.005. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict cscript.exe?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point