Windows: Kernel Driver Utility (KDU) and hamakaze.exe Execution

Alerts on KDU/hamakaze.exe launches with command-line parameters associated with kernel driver loading.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Matt Anderson, Dray Agha, Anna Pham (Huntress) (SigmaHQ), DRL 1.1
Published
2026-01-02
Updated
2026-07-30

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags process creation where the executable image ends with \\kdu.exe or hamakaze.exe and the command line contains KDU-specific options. KDU is used to interact with kernel driver loading mechanics, which can enable execution of unauthorized drivers and undermine security controls. The detection relies on Windows process creation telemetry, including the executable image path/name and the full command line arguments.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Suspicious TermService ServiceDll Hijack via Registry (via registry_set)
Suspicious Service Creation Named RDP-Controller via sc.exe (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Malicious Service Persistence via sc.exe Creating msdnetsvc
Suspicious Stately Taurus Masqueraded Service and Task Persistence via process_creation
Malicious Vulnerable Driver Load for EDR Evasion (via image_load)
Malicious Gelsemium OwlProxy wmipd DLL Load via image_load
Windows: Kernel Driver Utility (KDU) and hamakaze.exe Execution
Pivot detection · T1543.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.