LinuxT1005

>sed

Sed is a stream editor for filtering and transforming text. SUID sed allows reading sensitive files or modifying configuration entries.

Default Executable Paths

/usr/bin/sed
/bin/sed

Integrity & Metadata

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

Sed -e "" directly outputs input file lines to standard output.

Detection Engineering Notes

Detect sed commands targeting protected files.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

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

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:
Credential DumpPrivileges: User
T1005: Data from Local System

Reads all lines from /etc/shadow to standard output using SUID sed.

sed -e '' /etc/shadow

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (sed)

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

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain sed abuse.

Application Whitelisting

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

Attack Surface Reduction

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

Key operational questions and defensive answers about sed LOLBin tradecraft.

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

sed 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 Credential Dump—without dropping custom malware binaries on disk.

How do threat actors abuse sed in cyber intrusions?

Adversaries leverage sed to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "sed -e '' /etc/shadow" to achieve Credential Dump, masquerading behind legitimate system process lineage.

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

What MITRE ATT&CK techniques does sed map to?

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

How can organizations mitigate and restrict sed?

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