Microsoft-Signed Defender Driver Weaponized to Disable EDR and Antivirus

Microsoft Defender’s legitimate Boot-Time Removal driver, BTR.sys, can be repurposed to execute powerful kernel-level file and registry operations before many endpoint protections fully initialize.

The technique, disclosed by Check Point Research, is not a traditional vulnerability involving memory corruption, privilege escalation, or a coding flaw.

Instead, it shows how a trusted Microsoft-signed remediation component can be transformed into a Living-off-the-Land driver when an attacker reproduces its undocumented transaction protocol.

Microsoft-Signed Defender Driver Weaponized

BTR.sys is embedded in Microsoft Defender’s MpEngine.dll as the BOOTTIMETOOL resource. Defender deploys it when it must finish remediation after a reboot, such as deleting malware or other files that were locked while Windows was running.

During legitimate operations, the driver may be written under a randomly generated name, installed as a temporary service, and configured through an Alternate Data Stream (ADS) called :changelist.

Weaponizing Driver (Source: Checkpoint Research)
Weaponizing Driver (Source: Checkpoint Research)

This activity can look suspicious during incident response because it overlaps with techniques frequently associated with kernel-level malware loaders.

However, BTR.sys is part of Defender’s normal remediation architecture and typically removes its files and service entries after completing queued operations.

Check Point researchers reverse-engineered the driver’s proprietary transaction format and created a proof-of-concept utility called BTR_CLI. The tool generates transaction blobs accepted by BTR.sys, allowing the driver to be staged and executed with attacker-controlled operations.

The configuration is protected with RC4 encryption and integrity verification based on a modified CRC-32 mechanism. Once accepted, the transaction can instruct the signed driver to delete files and directories, move files, delete registry keys or values, and write registry data.

Because BTR.sys performs these actions in Ring 0, an attacker who already holds administrative privileges could use it to tamper with protected endpoint security assets.

The most significant concern is the driver’s position in the Windows startup sequence. BTR.sys operates as a system-start driver, rather than a boot-start driver, because its initialization requires filesystem access.

 Jiří Vinopal found that assigning it to the early Boot Bus Extender load-order group could allow it to run after the filesystem becomes available but before numerous user-mode EDR and antivirus components launch.

This creates what researchers describe as a “golden window.” In that interval, the driver could remove security binaries, alter service registry configuration, or otherwise disrupt security tooling before those products establish their normal protection stack.

Weaponzing Driver (Source: Checkpoint)
Weaponzing Driver (Source: Checkpoint)

The approach differs from Bring Your Own Vulnerable Driver attacks, where threat actors load a legitimately signed but flawed third-party driver to obtain kernel-level execution.

BTR.sys is not known to be vulnerable; it is a built-in Microsoft component whose intended remediation capabilities can be invoked through a recreated configuration protocol. Its valid Microsoft signature may also complicate controls that rely heavily on signature reputation or driver blocklists.

Check Point said it had found no evidence of active exploitation when its research was published. Nevertheless, the public methodology increases the need for proactive monitoring.

Defenders should watch for unusual BTR.sys deployment context, rather than treating a Microsoft signature as sufficient proof of legitimacy. Sysmon Event ID 15, FileCreateStreamHash, can help identify suspicious .sys:changelist ADS creation.

Sysmon Event ID 6, DriverLoad, can provide useful visibility into signed driver loads and associated hashes.

High-confidence signals include BTR.sys being deployed by PowerShell, command shells, unsigned executables, or processes outside the expected Defender lineage.

Other warning signs include randomized service keys containing Args references to :changelist, unexpected Boot Bus Extender assignments, rapid BootClean.log activity, and SYSTEM-level deletion of antivirus or EDR binaries immediately after a Microsoft-signed driver load.

Organizations should tightly control SeLoadDriverPrivilege, audit boot-time service changes, collect ADS and driver-load telemetry, and investigate suspicious kernel operations attributed to the System process.

Give your security team the visibility and context to investigate suspicious activity faster and contain threats before business impact grows. Strengthen Your Investigations with ANY.RUN

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories