Windows ProcDump Execution via Renamed Binary

Flags renamed ProcDump usage on Windows by matching procdump indicators and dump flags while excluding known executable names.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-11-18
Updated
2026-07-30

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 Windows process executions where the binary’s OriginalFileName corresponds to procdump while the command line contains ProcDump dump-related flags and /accepteula. It also excludes common legitimate ProcDump filenames by filtering out process images ending with known procdump executables, focusing on renamed copies. Attackers and malware may rename ProcDump to evade security controls while still using familiar dumping options.

Related detections9 linkedT1036.003 — drag to rearrange
Suspicious Renamed PowerShell Binary Execution (via process_creation)
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
Windows ProcDump Execution via Renamed Binary
Pivot detection · T1036.003 · 9 related

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