Windows Process Creation: Renamed Sysinternals Sdelete Execution

Alerts on Windows processes created with OriginalFileName sdelete.exe but executed via renamed sdelete binary paths.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-06
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 executions where the process has an OriginalFileName of sdelete.exe, but the running image path ends with sdelete.exe (or sdelete64 variants) rather than being invoked as the original binary name. Renaming legitimate tools is a common way to evade allowlists and detection rules, and it can also indicate intentional misuse of a disk-wiping utility. It relies on Windows process creation telemetry, specifically the OriginalFileName field and the executable image path.

Related detections9 linkedT1485 — drag to rearrange
Malicious JADEPUFFER Ransom Database Table Manipulation
Suspicious Self-Deleting Batch Script Execution Consistent with Agonizing Serpens Wiper Cleanup
Malicious Mass Device Wipe via Intune Remote Actions (via m365)
Malicious S3 Bucket Deletion During Bling Libra Extortion
Malicious DYNOWIPER PowerShell Loader Execution (via ps_script)
Suspicious S3 Lifecycle Policy Set for Rapid Object Deletion
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
Windows Process Creation: Renamed Sysinternals Sdelete Execution
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.