Windows Process Creation: SDelete Used for File Overwrite

Alerts when sdelete.exe runs in a way consistent with file overwrite to impede forensic recovery.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
frack113 (SigmaHQ), DRL 1.1
Published
2021-06-03
Updated
2026-07-30

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule flags Windows process executions where the binary name is sdelete.exe and the command line does not match patterns associated with alternate behavior (e.g., specific flags like -h, -c, -z, or the help switch). SDelete can be used to overwrite file contents rather than just free space, which can reduce forensic artifacts and hinder incident response. The detection relies on process creation telemetry, specifically the executable filename and command-line arguments.

Related detections9 linkedT1485 — drag to rearrange
Malicious PathWiper Loader Script Execution from Windows Temp via WScript
Suspicious Free Space Wipe via cipher.exe
Suspicious sha256sum.exe Execution from Windows Temp Directory
Suspicious Secure Deletion of Free Space via Cipher (via process_creation)
HamsaUpdate Wiper Trigger via F5UPDATER ConfirmDeleteFiles Argument (via process_creation)
Malicious Scheduled Task Deploying DYNOWIPER Payload (via process_creation)
Malicious Mini Shai-Hulud TanStack Destructive rm Killswitch (via process_creation)
Malicious S3 Object Encryption with Customer Provided Key via CopyObject
Malicious Cloud Storage Destruction by Cloud Build Service Account
Windows Process Creation: SDelete Used for File Overwrite
Pivot detection · T1485 · 9 related

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