Microsoft's Four-Year-Old Patch Had a Door APT41 Walked Through
Kaspersky says a China-linked hacking group used a bootkit called BlackX to beat Secure Boot on fully patched Windows machines, because Microsoft's 2022 fix was never turned on by default.

A diplomat's laptop in Central Asia checked out clean. Windows Update showed every box ticked. Underneath the operating system, before Windows had any say in the matter, a bootkit was already running.
That's the find Kaspersky published in October: a UEFI bootkit called BlackX, discovered during an espionage campaign targeting diplomatic organisations in Central Asia, with victims including organisations in Tajikistan, Uzbekistan and Turkmenistan. A fully patched machine got compromised below the operating system, and the patch did exactly what Microsoft built it to do. It just never finished the job.
The Patch That Needed a Second Patch
BlackX exploits "Baton Drop," a flaw in the Windows boot manager that can bypass Secure Boot and extract BitLocker encryption keys. The CVE became public in 2022. Microsoft patched it that year but did not revoke trust in the certificate used to sign older vulnerable boot managers. That gap is the whole story.
Microsoft's mitigation requires updating Secure Boot trust databases and explicitly revoking Windows Production PCA 2011 through the forbidden-signature database, or DBX. These mitigations are not enabled by default.
Microsoft let the old certificate expire this fall, which sounds like closure. It isn't. Translation: the thing that sounds like a fix is a scheduling event. The actual fix is a manual step most administrators never knew existed.
Microsoft has a defense. Administrators must deploy updated trust certificates and boot managers before revoking older trust; force-revoking a certificate bricks recovery drives, installation media, and network boot services using older signed components. That's a real tradeoff. It is also a four-year tradeoff that nobody loudly told customers they were still carrying.
Patch Tuesday is a calendar. It was never a perimeter.

Kaspersky attributes the campaign to APT41, the prolific Chinese threat actor also known as Winnti and Double Dragon, with medium confidence. That's a hedge, not a shrug: intellectual honesty about the confidence level, which most vendor attributions skip.
Important caveat: these machines weren't infected from the factory. In the observed attacks, operators first compromised victim environments and obtained administrator privileges before deploying the bootkit. BlackX is a persistence tool for attackers already inside, not a supply-chain contamination.
The malware's housekeeping is almost funny. Its kernel driver can redirect requests and launch Windows Calculator instead whenever a security tool tries to inspect its files. Less cute: it specifically targeted Kaspersky and Avast; the attacker knew exactly which vendors they expected to meet on a diplomatic network.
Microsoft shipped a mitigation it never flipped on by default, for reasons that were defensible in isolation, and a state-linked hacking group found the unlocked door roughly four years later.
If you administer Windows fleets: every victim ran a fully patched Windows release, and the fix only works if an admin manually revokes the Windows Production PCA 2011 certificate through DBX. Go check your DBX. Patch compliance dashboards will not tell you if you skipped it.
What to watch: whether Microsoft now forces the DBX revocation by default, whether Kaspersky's telemetry turns up BlackX victims outside the three diplomatic missions it named, and whether the BlackLotus code lineage produces more copycats now that the technique is public.
- BlackX UEFI bootkit exploits Baton Drop flaw to bypass Secure Boot
- BlackX UEFI Bootkit Bypasses Secure Boot on Fully Patched Windows Systems
- Chinese Hackers Breached Diplomatic Networks; Microsoft Baton Drop Enforcement Never Deployed
- Suspected Chinese APT41 Hackers Use BlackX Bootkit to Bypass Windows Secure Boot
- BlackX UEFI bootkit: what it is, who it targets and what to do on Windows
- New BlackX UEFI Bootkit Bypasses Windows Secure Boot Even After Security Updates
- BlackX UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame?
- UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame?
- BlackX UEFI Bootkit Infects Patched Windows via Secure Boot Ambiguity
- UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame? - Baraza
- UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame? - Lemmy.World
- UEFI Bootkits: The Malware That Lives Below Your Operating System — Hive Security
- Cinemark CEO says Netflix’s release window led chain to reject Imax screenings for ‘Cliff Booth’
- Techrights — Intercontinental Brigading - Part XXXI - Microsoft and Promoters of "Secure Boot" Are to Blame
- BlackLotus UEFI bootkit: Myth confirmed
- [March 6, 2023] Ars Technica: Stealthy UEFI malware fully bypassing Secure Boot found in the wild enabled by unpatchable Windows flaw News
- BlackX UEFI bootkit bypasses Secure Boot via unrevoked bootloaders
- Unkillable UEFI Malware Bypassing Secure Boot Enabled By Unpatchable Windows Flaw - Slashdot
- BlackX UEFI Bootkit Revives Baton Drop on Patched Windows Hosts That Skipped DBX Revocation - DEV Community
- BlackX UEFI Bootkit Bypasses Windows Secure Boot
- What the BlackX bootkit means for patched Windows PCs — Pickuma
- BlackX Bootkit Found a Trust Gap on Patched Windows PCs
- APT41 Deploys BlackX UEFI Bootkit Against Central Asian Diplomatic Agencies