Researchers find way to weaponize Windows Defender’s own driver

In a recent revelation by Check Point Research, a novel technique has emerged that utilizes a legitimate component of Windows Defender to execute kernel-level operations on Windows systems, spanning from Windows 7 to Windows 11 25H2. This method, intriguingly, does not hinge on exploiting any software vulnerabilities, but rather leverages the boot-time remediation driver, known as BTR.sys, which is already integrated within Microsoft Defender.

Unveiling the Mechanism

The BTR.sys driver, embedded in Defender’s MpEngine.dll, was originally designed to facilitate the removal of malware components that are locked during system operation. Researchers undertook the task of reverse-engineering its undocumented transaction protocol, uncovering that it employs RC4 encryption coupled with a hard-coded key. This discovery paved the way for the development of a proof-of-concept tool named BTR_CLI, which can extract the driver and construct encrypted transactions to install it as a service. Notably, this process circumvents standard service management and logging protocols.

Capabilities of BTR.sys

Once operational, BTR.sys executes commands from Ring 0, granting it the capability to perform a variety of critical operations. These include:

  • Deleting or moving files
  • Modifying registry entries
  • Removing security binaries, including components of Defender itself

This can occur during a specific “golden window,” a brief period when the file system is writable but before Defender’s user-mode services are initiated.

Access Requirements and Implications

To exploit this technique, an attacker must possess administrator privileges, specifically the SeLoadDriverPrivilege. While Microsoft has indicated that this method does not warrant immediate servicing, as it relies on pre-existing administrative access, the potential for exploitation remains a concern. Although there have been no documented instances of this technique being utilized in real-world attacks, it underscores a significant architectural trust boundary that could be manipulated by an attacker with adequate privileges.

Winsage
Researchers find way to weaponize Windows Defender’s own driver