Ars TechnicaDan Goodin
Kaspersky finds BlackX bootkit bypassing Secure Boot on Windows
Part of the bootkit story · since 22 Oct
- Thu 22 Oct, 06:07 UTC. Securelist, first report. BlackX UEFI bootkit targets Central Asian diplomats via Secure Boot flaw.
- Thu 22 Oct, 11:41 UTC. SecurityOnline, its first report on the story. APT41 Uses a BlackX UEFI Bootkit to Bypass Secure Boot in Central Asia.
- Fri 23 Oct, 19:48 UTC. The Hacker News, its first report on the story. BlackX Bootkit Bypasses Secure Boot in Central Asian Attacks.
- Tue 3 Nov, 17:01 UTC. Ars Technica, its first report on the story. Kaspersky finds BlackX bootkit bypassing Secure Boot on Windows. This article, 4th of 4.
Kaspersky has identified organisations infected with BlackX, a UEFI bootkit that can bypass Secure Boot on Windows machines despite the systems having Microsoft’s relevant updates installed. BlackX exploits CVE-2022-21894, known as “Baton Drop”, a logic flaw in the Windows boot manager. The flaw can let attackers run unauthorised boot code; in some circumstances, it can also expose BitLocker encryption keys.
By executing early in the boot process, BlackX can load a malicious driver into the Windows kernel before many operating-system and security defences are active. Bootkits can be hard to detect and may survive an operating-system reinstall if the infected boot partition remains.
Microsoft fixed the underlying flaw in 2022, but the fix did not revoke trust in older vulnerable boot managers. Updates issued from May 2023 introduced a new signing certificate, and a further mitigation in 2024 provided a way to add the old Windows Production PCA 2011 certificate to Secure Boot’s forbidden-signatures database. Kaspersky says installing updates alone is not enough: most administrators must take an additional step to activate the revocation.
The firm argues that the instructions are difficult to find and that administrators may not realise action is required. Microsoft directed customers to a Knowledge Base post published two weeks before the infections were reported; the source says that post does not warn that patches alone leave systems exposed to Baton Drop attacks.
Kaspersky believes BlackX’s operators took advantage of organisations failing to activate the mitigation, and may have studied BlackLotus to create a copycat bootkit. The source does not report how many organisations were infected or confirm that BlackX has been used beyond the identified cases.
How the story developed
4 articles from 4 outlets since 22 Oct. Picked up again today after 11 days quiet. This was the 4th report, 12 days after the first.
- Thu 22 Oct, 06:07 UTC. Securelist, first report. BlackX UEFI bootkit targets Central Asian diplomats via Secure Boot flaw.
- Thu 22 Oct, 11:41 UTC. SecurityOnline, its first report on the story. APT41 Uses a BlackX UEFI Bootkit to Bypass Secure Boot in Central Asia.
- Fri 23 Oct, 19:48 UTC. The Hacker News, its first report on the story. BlackX Bootkit Bypasses Secure Boot in Central Asian Attacks.
- Tue 3 Nov, 17:01 UTC. Ars Technica, its first report on the story. Kaspersky finds BlackX bootkit bypassing Secure Boot on Windows. This article, 4th of 4.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 4 articles as a listHide the list
- Thu 22 OctDay 02
- BlackX UEFI bootkit targets Central Asian diplomats via Secure Boot flaw06:07 · Securelist · First report
- APT41 Uses a BlackX UEFI Bootkit to Bypass Secure Boot in Central Asia11:41 · SecurityOnline
- Fri 23 OctDay 11
- BlackX Bootkit Bypasses Secure Boot in Central Asian Attacks19:48 · The Hacker News
Quiet for 11 days
Tue 3 NovDay 121- Kaspersky finds BlackX bootkit bypassing Secure Boot on Windows17:01 · Ars Technica · Picked up again · This article, 4th of 4