Suspicious Renamed Windows Debugger CDB Execution

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-18
Updated
2026-09-18

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 detects execution of the Microsoft console debugger CDB under a renamed file name, a defense evasion technique seen in the REF7707 campaign. CDB is a signed LOLBin that can launch arbitrary commands and shellcode so attackers rename it to evade name based detection. A mismatch between the original file name CDB.exe and the on-disk image name surfaces this abuse.

Related detections9 linkedT1218 — drag to rearrange
Suspicious Scripting Interpreter Execution From Downloads Or Temp via Reputation Hijacking
Suspicious MMC Console Spawning Script Interpreter via GrimResource
Suspicious MMC Console Loading MSC File From User Writable Path
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Malicious regsvcs LOLBin Loading Ransomware DLL from UNC Path
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Suspicious Extexport DLL Side-Loading Execution
Suspicious Renamed Windows Debugger CDB Execution
Pivot detection · T1218 · 9 related

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