Malicious Bring-Your-Own-Vulnerable-Driver Load By BlackByte

PremiumReviewedSigma · High · v1
Product
windows
Category
image_load
Author
HuntRule
Published
2026-05-11
Updated
2026-08-28

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects loading of vulnerable kernel drivers abused by BlackByte to disable endpoint protection. BlackByte deployed the RtCore64 DBUtil_2_3 zamguard64 and gdrv vulnerable drivers to gain kernel-level code execution. Loading a known-vulnerable signed driver is a BYOVD technique that lets attackers terminate security products and tamper with the kernel.

Related detections9 linkedT1068 — drag to rearrange
Windows Audit-CVE: User Applications Writing CveEventWrite Events (Event ID 1)
Malicious Looney Tunables Privilege Escalation Exploit by Kinsing (via process_creation)
Malicious Kerberos proxiable/S4U2self Ticket - CVE-2021-42278/42287 (via security)
Malicious Vulnerable Driver HwRwDrv Loaded for BYOVD
Possible CopyFail Root Exploitation via Python Spawning SUID Shell (via process_creation)
Malicious ESX Admins Domain Group Creation via Process Creation
Suspicious lmadmin License Manager DLL Sideload from Public Path via image_load
Suspicious Desktop Window Manager Spawning Shutdown Utility via Process Creation
Suspicious Masqueraded Zemana Driver Written to Disk via updatedrv (via file_event)
Malicious Bring-Your-Own-Vulnerable-Driver Load By BlackByte
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.