DEV Community

Cover image for Bring Your Own Vulnerable Driver (BYOVD): How Attackers Silence Antivirus from the Kernel
Anish Banerjee
Anish Banerjee

Posted on

Bring Your Own Vulnerable Driver (BYOVD): How Attackers Silence Antivirus from the Kernel

Examining the threat data from July 2026 paints a terrifying picture of virtually all the notable ransomware operations—from Qilin to Warlock and Reynolds—whereby by the time the encryptor has completed its operations, the security solution has already been incapacitated.
Ransomware affiliates have given up on beating Endpoint Detection and Response (EDR) software and have instead turned to taking it down, and the means of supporting this assault has come to involve the Bring Your Own Vulnerable Driver (BYOVD) technique.

Here is how attackers are weaponizing Microsoft's trust model against itself to blind security teams before the real attack begins.

1. The Kernel Access Problem
In order to comprehend what BYOVD is, one is required to understand where security software is located. A modern EDR solution functions at the kernel level of the operation system (Ring 0), which is the most prominent and deepest layer of Windows operation system. Being in that layer, the EDR solution can detect any process in motion, terminate malicious processes, and defend itself from getting shut down by either an ordinary user or an administrator.
Whenever an attacker manages to get hold of administrative privileges usually via infostealers or initial access brokers mentioned previously, they cannot just click "uninstall" button on the agent of the enterprise. The EDR has got self-protection measures. In order to get rid of EDR solution, an attacker is required to access kernel as well.
However, it is important to mention that Windows has a principle that states that no code can be loaded into the kernel without a digitally signed driver from a reputable certificate authority. Attackers do not have the privilege to digitally sign their corrupt drivers.

2. The BYOVD Loophole
At this point, we can introduce BYOVD. Rather than using malware, the cybercriminal uses a legitimate, approved driver from a recognized vendor. The driver could be something like an outdated version of a motherboard utility, antivirus, or even game anti-cheating software.
As Windows verifies the signature of the driver as valid, it loads it into the kernel without any suspicion of danger. Once the driver is in the kernel, the hacker takes advantage of a known vulnerability and gains complete read/write authority.

3. The "EDR Killer" Execution
Once inside the kernel, the attacker deploys an automated tool known on underground forums as an "EDR Killer" (such as EDRKillShifter or Terminator).
These tools use the exploited driver to bypass the EDR’s self-protection (often called PPL - Protected Process Light). They systematically rip out the security software’s core components:
They unhook the kernel callbacks, which blinds the EDR from seeing new processes.
They forcefully terminate the security agent's processes.
They disable telemetry reporting back to the corporate security team.
In a matter of seconds, an environment protected by top-tier security tools is plunged into total darkness. The attacker is now free to deploy ransomware, scrape memory for credentials, or exfiltrate data without generating a single alert.

4. The EaaS (Evasion-as-a-Service) Market
The reason this threat is so widespread in 2026 is due to commodification. There is no need for a ransomware affiliate to have knowledge of creating kernel exploits. There's now a bustling market for "plug-and-play" EDR killers on the dark web. Affiliates merely have to buy a finished product, including a vulnerable driver. Recently, threat intelligence observed the existence of 90 versions of EDR killers that have been used.

The Shift to Pre-Execution Defense
Depending on an EDR is a poor plan to defend against a BYOVD assault. By the time the compromised driver is acquired, the fight is typically already lost.
To defend, strict hygiene must be implemented. Microsoft’s Vulnerable Driver Blocklist (WDAC) must be rigorously enforced, as must Hypervisor-Protected Code Integrity (HVCI). Additionally, defenses against BYOVD must include monitoring for signs of impending BYOVD. Since attackers must first gain elevated privileges before they can use BYOVD, defenses must focus on finding theft of credentials, suspicious RDP logins.

DarkX — DarkX provides the external intelligence required to disrupt the BYOVD kill chain, continuously monitoring dark web forums for the sale of compromised administrative credentials and alerting organizations to newly circulating EDR killer toolsets before they are deployed against the enterprise.

For more research on cybersecurity, privacy, and emerging digital risks, visit:
IntelligenceX - IntelligenceX enables users to discover digital evidence in a privacy-friendly way.

Top comments (0)