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
Suspicious Dell ControlVault DLL Load by Unexpected Process (ReVault)
Suspicious Vulnerable ASUS AsIO3.sys Driver Load
Windows Audit-CVE: User Applications Writing CveEventWrite Events (Event ID 1)
Malicious Payload Download From copy.fail Exploit Host on Linux (via process_creation)
Suspicious su Execution From Uncommon Parent Process on Linux (via process_creation)
Possible noPac sAMAccountName Spoofing via Machine Account Rename
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Suspicious CLFS Base Log File Created in SkyPDF ProgramData Path during Zero-Day Exploitation (via file_event)
Malicious Cisco SD-WAN Tenant List Upload Script Execution (via process_creation)
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.