>base64

Base64 encodes or decodes standard input or files to standard output. Attackers abuse it to read sensitive files without user permissions (when SUID) or decode obfuscated payload stages.

Default Executable Paths

/usr/bin/base64
/bin/base64

Integrity & Metadata

Original Name: base64
File Version: GNU coreutils
Category Count: 1 weaponized patterns
Forensics & Triage Insight

Running base64 on /etc/shadow or confidential tokens allows reading restricted content without modification.

Detection Engineering Notes

Look for base64 invoked against sensitive files like /etc/shadow, /etc/security, or private keys (.ssh/id_rsa).

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

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

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:
Defense EvasionPrivileges: User
T1140: Deobfuscate/Decode Files or Information

Reads the content of restricted files by encoding to base64 and decoding back to standard output.

base64 /etc/shadow | base64 --decode

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (base64)

Validated against MITRE T1005, T1140
base64 Microsoft Defender Querykql
1DeviceProcessEvents | where FileName =~ "base64" | where ProcessCommandLine has_any ("/etc/shadow", "/etc/sudoers", ".ssh/id_rsa", "/root/") | project Timestamp, DeviceName, AccountName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain base64 abuse.

Application Whitelisting

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

Attack Surface Reduction

Implement AppArmor or SELinux profiles restricting base64 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) • base64

Key operational questions and defensive answers about base64 LOLBin tradecraft.

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

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

How do threat actors abuse base64 in cyber intrusions?

Adversaries leverage base64 to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "base64 /etc/shadow | base64 --decode" to achieve Defense Evasion, masquerading behind legitimate system process lineage.

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

What MITRE ATT&CK techniques does base64 map to?

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

How can organizations mitigate and restrict base64?

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