1-minute read of a 5 min report

Microsoft Defender Driver Lets Admins Delete Security Tools at Boot

By

1-minute read

What a defender needs to know

Check Point researcher Jiří Vinopal reverse-engineered Microsoft Defender’s signed BTR.sys cleanup driver and reproduced valid encrypted transactions that delete or move files and alter registry keys in kernel mode. With SeLoadDriverPrivilege, an administrator can stage the driver for early boot and remove Defender binaries or service keys before user-mode protection starts. The technique is post-compromise, and Check Point found no in-the-wild abuse.

The driver normally arrives from MpEngine.dll under a random eight-letter .sys name and reads an RC4-encrypted :changelist alternate data stream. Check Point tested the primitive from Windows 7 build 7601 through Windows 11 25H2. Microsoft declined immediate servicing, according to the researcher, because administrative privilege is already required.

Collect Sysmon events 6, 11, 12, 13, 15, and 23 plus System event 7045 across the reboot. Search for .sys:changelist, .sys:*.dat, Boot Bus Extender, \SystemRoot\Temp\BootClean.log, and service Args values that point to :changelist. Correlate driver lineage, PID 4 file deletion, and changes to the WdFilter or WinDefend service keys.

A controlled Defender remediation should create the driver through a Defender process and the Service Control Manager, write feedback under Defender’s RebootActions directory, produce event 7045, and leave Defender binaries and service keys intact. Compare that expected sequence with direct registry staging, driver-local feedback streams, and kernel deletion of security controls. Investigate the administrator session and the preceding compromise when those abuse markers appear.

Primary sources