Malicious Vulnerable Driver Mapping via KDU

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

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  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 Kernel Driver Utility kdu.exe with its provider and driver-mapping flags, a bring-your-own-vulnerable-driver technique observed in the ESXi exploitation activity to load unsigned kernel code. KDU abuses a signed vulnerable driver to map an attacker driver such as MyDriver.sys into the kernel, defeating driver signature enforcement. Presence of kdu.exe with these arguments indicates kernel-level defense evasion.

Related detections9 linkedT1068 — drag to rearrange
SwimSnake Kernel Driver Service Creation from Public Directory via sc.exe (via process_creation)
Masquerading Kerberos Ticket Without a Trailing $ - CVE-2021-42278/42287 (via security)
Malicious MinPlasma_CVE-2020-17103 - Reg via Sysmon (via registry_event)
Suspicious OverlayFS Mount with Writable Upperdir for GameOverlay Exploitation (via process_creation)
Suspicious Unprivileged User Namespace Creation via unshare for OverlayFS Exploitation (via process_creation)
Suspicious su to Root with Blank Invoking User for CopyFail LPE (via auth)
Suspicious Delayed AF_ALG PF_ALG Protocol Registration for CopyFail LPE (via syslog)
Suspicious CrazyHunter BYOVD Driver Drop in Public Directory
Malicious Diamorphine Rootkit Kernel Module Load via insmod
Malicious Vulnerable Driver Mapping via KDU
Pivot detection · T1068 · 9 related

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