>tar

GNU tar is an archiving utility. Attackers abuse tar checkpoint execution options (--checkpoint-action=exec) to spawn an interactive shell or execute arbitrary commands when running with sudo or SUID permissions.

Default Executable Paths

/usr/bin/tar
/bin/tar

Integrity & Metadata

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

Checkpoint actions in tar allow running arbitrary commands periodically during archive processing, frequently abused in wildcards or automated backup scripts.

Detection Engineering Notes

Monitor process creation of tar containing "--checkpoint" and "--checkpoint-action=exec".

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

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

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

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

Abuses GNU tar checkpoint parameters to spawn an interactive shell.

tar -cf /dev/null /dev/null --checkpoint=1 --checkpoint-action=exec=/bin/sh

SIEM & EDR Detection Rules

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

Telemetry & SIEM Detection Suite (tar)

Validated against MITRE T1059.004, T1548.001
tar Microsoft Defender Querykql
1DeviceProcessEvents | where FileName =~ "tar" | where ProcessCommandLine has_all ("--checkpoint", "--checkpoint-action=exec") | project Timestamp, DeviceName, AccountName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain tar abuse.

Application Whitelisting

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

Attack Surface Reduction

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

Key operational questions and defensive answers about tar LOLBin tradecraft.

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

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

How do threat actors abuse tar in cyber intrusions?

Adversaries leverage tar to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "tar -cf /dev/null /dev/null --checkpoint=1 --checkpoint-action=exec=/bin/sh" to achieve Execute, masquerading behind legitimate system process lineage.

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

What MITRE ATT&CK techniques does tar map to?

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

How can organizations mitigate and restrict tar?

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