MITRE ATT&CK T1059.004: Unix Shell
When to use this skill
Use this skill when the task involves T1059.004, Unix Shell, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1059.004
- Technique name: Unix Shell
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1059/004
- Tactics: execution
- Platforms: ESXi, Linux, macOS, Network Devices
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution.(Citation: DieNet Bash)(Citation: Apple ZShell) Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.
Unix shells also support scripts that enable sequential execution of commands as well as other typical programming operations such as conditionals and loops. Common uses of shell scripts include long or repetitive tasks, or the need to run the same set of commands on multiple systems.
Adversaries may abuse Unix shells to execute various commands or payloads. Interactive shells may be accessed through command and control channels or during lateral movement such as with SSH. Adversaries may also leverage shell scripts to deliver and execute multiple commands on victims or as part of payloads used for persistence.
Some systems, such as embedded devices, lightweight Linux distributions, and ESXi servers, may leverage stripped-down Unix shells via Busybox, a small executable that contains a variety of tools, including a simple shell.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- 2025 Poland Wiper Attacks (campaign)
- APT41 (intrusion-set)
- Anchor (malware)
- AppleJeus (malware)
- Aquatic Panda (intrusion-set)
- BOLDMOVE (malware)
- BPFDoor (malware)
- BRICKSTORM (malware)
- Bundlore (malware)
- CASTLETAP (malware)
- COATHANGER (malware)
- CallMe (malware)
- Chaos (malware)
- CoinTicker (malware)
- Contagious Interview (intrusion-set)
- CookieMiner (malware)
- Cuckoo Stealer (malware)
- Derusbi (malware)
- Doki (malware)
- Drovorub (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ent-t1059-004-unix-shell3description: "Analyze MITRE ATT&CK T1059.004 Unix Shell in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1059.004, Unix Shell, or enterprise ATT&CK. Adversaries may abuse Unix shell commands and scripts for execution."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1059-004-unix-shell7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1059.00410 attack_stix_id: attack-pattern--a9d4b653-6915-42af-98b2-5758c4ceee5611 attack_version: "1.4"12 attack_modified: "2025-10-24T17:49:12.476Z"13---1415# MITRE ATT&CK T1059.004: Unix Shell1617## When to use this skill1819Use this skill when the task involves T1059.004, Unix Shell, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1059.00425- Technique name: Unix Shell26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1059/00428- Tactics: execution29- Platforms: ESXi, Linux, macOS, Network Devices30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution.(Citation: DieNet Bash)(Citation: Apple ZShell) Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.3738Unix shells also support scripts that enable sequential execution of commands as well as other typical programming operations such as conditionals and loops. Common uses of shell scripts include long or repetitive tasks, or the need to run the same set of commands on multiple systems.3940Adversaries may abuse Unix shells to execute various commands or payloads. Interactive shells may be accessed through command and control channels or during lateral movement such as with [SSH](https://attack.mitre.org/techniques/T1021/004). Adversaries may also leverage shell scripts to deliver and execute multiple commands on victims or as part of payloads used for persistence.4142Some systems, such as embedded devices, lightweight Linux distributions, and ESXi servers, may leverage stripped-down Unix shells via Busybox, a small executable that contains a variety of tools, including a simple shell.4344## Agent workflow45461. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.472. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.483. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.494. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.505. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.516. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5253## Bundled resources5455- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.56- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.57- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.58- `templates/detection-brief.md`: detection engineering brief template.59- `templates/hunt-plan.md`: threat hunt plan template.60- `templates/incident-response-note.md`: incident response note template.61- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.62- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.63- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6465To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6667## Detection guidance6869No ATT&CK detection guidance was present in the source STIX object.7071## Useful telemetry and data sources7273- Not specified in the STIX object.7475## Mitigations to consider7677- Execution Prevention7879## Known threat context8081Use these examples only as contextual leads, not as proof that an observed event is this technique:8283- 2025 Poland Wiper Attacks (campaign)84- APT41 (intrusion-set)85- Anchor (malware)86- AppleJeus (malware)87- Aquatic Panda (intrusion-set)88- BOLDMOVE (malware)89- BPFDoor (malware)90- BRICKSTORM (malware)91- Bundlore (malware)92- CASTLETAP (malware)93- COATHANGER (malware)94- CallMe (malware)95- Chaos (malware)96- CoinTicker (malware)97- Contagious Interview (intrusion-set)98- CookieMiner (malware)99- Cuckoo Stealer (malware)100- Derusbi (malware)101- Doki (malware)102- Drovorub (malware)103104## Recommended output pattern105106When responding with this skill, structure the answer as:107108- Assessment: whether the evidence supports this ATT&CK mapping and why.109- Evidence: specific indicators, logs, behaviors, and assumptions.110- Detection: telemetry sources, analytic logic, and tuning considerations.111- Response: containment, eradication, recovery, and validation actions.112- Coverage gaps: missing logs, sensors, controls, or environmental details.113- References: include the ATT&CK URL and any user-provided evidence references.