macOS Process Execution: dd and truncate used for binary padding

Flags macOS dd plus truncate command lines consistent with adding junk data for binary padding.

FreeReviewedSigma · High · v2
Product
macos
Category
process_creation
Author
Igor Fits, Mikhail Larin, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-19
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies macOS process executions where an attacker uses dd to append or generate junk data for binary padding (e.g., using /dev/zero, /dev/random, or /dev/urandom) and uses truncate with a size argument (via -s +). Altering the on-disk representation of malware via padding can help evade static detection and change file hashes without changing core functionality. It relies on process creation telemetry capturing the executable path and command-line arguments for dd and truncate.

Related detections2 linkedT1027.001 — drag to rearrange
Linux: Detect dd and truncate used to pad binaries and alter file contents
Windows Security: Failed Code Integrity Checks (Event 5038/6281)
macOS Process Execution: dd and truncate used for binary padding
Pivot detection · T1027.001 · 2 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.