Linux dd Process Memory Map Overwrite for Code Injection (proc/mem)

Alerts when dd is used to write to /proc/<pid>/mem, suggesting potential Linux process code injection.

FreeReviewedSigma · Medium · v3
Product
linux
Category
process_creation
Author
Joseph Kamau (SigmaHQ), DRL 1.1
Published
2023-12-01
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies potential process code injection on Linux by spotting use of the dd utility with arguments consistent with overwriting another process’s memory via /proc/<pid>/mem. Attackers can leverage this pattern to modify a target process without the same visibility as ptrace-based approaches, making it relevant for stealth and privilege-focused scenarios. Detection relies on process creation telemetry that includes the executed Image path and CommandLine arguments containing of=, /proc/, and /mem.

Related detections2 linkedT1055.009 — drag to rearrange
Malicious Process Memory Injection via dd Write to /proc/pid/mem by UNC3886 (via process_creation)
Linux: Disable ASLR via personality syscall or sysctl/randomize_va_space changes
Linux dd Process Memory Map Overwrite for Code Injection (proc/mem)
Pivot detection · T1055.009 · 2 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. 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.