Zero Day Room
Live
Vulnerabilities

BlackX Bootkit Targets Central Asian Diplomats via Patch Flaw

APT41 deployed the BlackX UEFI bootkit against diplomatic agencies in Central Asia by exploiting a critical Microsoft patch that requires manual activation, leaving fully updated systems vulnerable.

APT41 deployed the BlackX UEFI bootkit against diplomatic agencies in Central Asia by exploiting a critical Microsoft...

A modernised bootkit dubbed BlackX has been used in attacks against diplomatic organisations in Tajikistan, Uzbekistan, and Turkmenistan. The campaign, attributed to the China-linked APT41 group, successfully bypassed Secure Boot protections on fully patched systems by exploiting an inefficiency in the deployment of a critical Microsoft security update known as Baton Drop.

In October 2022, a hacking forum advertised a UEFI bootkit called BlackLotus for $5,000. Kaspersky GReAT said: "Given the low price for such powerful capabilities, the cybersecurity community initially took this advertisement with a grain of salt." No samples were found initially, but in March 2023, ESET confirmed BlackLotus was genuine and could bypass Secure Boot via the Baton Drop vulnerability, tracked as CVE-2022-21894. Microsoft subsequently released multiple security updates to address it.

BlackX Campaign Targeting Diplomatic Targets

In early 2026, a malware sample remarkably similar to BlackLotus was deployed in an advanced persistent threat campaign across Central Asia. Dubbed BlackX, this bootkit was installed after attackers first compromised target networks and obtained administrator privileges.

Attackers deployed two files: an installer named inst.exe and an RC4-encrypted, extensionless file named PVMDIJGKAX2. The installer was launched with a command line where the final argument served as the RC4 decryption key. The package dropped files to both the system and UEFI partitions to exploit the Baton Drop vulnerability, implementing a method nearly identical to the original BlackLotus to install custom Machine Owner Keys and load arbitrary EFI files. One payload, OxiDLLRunner, was obfuscated with OLLVM, a tool commonly used by Chinese-speaking actors.

Technical Implementation and Persistence Mechanisms

The attackers behind BlackX likely reverse-engineered or purchased the original BlackLotus code, as it was never published. The UEFI payload injects a malicious driver into the Windows kernel, signed with a now-revoked certificate belonging to a Chinese entity. This driver performs several critical evasion functions.

A key finding was that targeted machines were fully patched. The Baton Drop patch is designed to revoke the 'Windows Production PCA 2011' certificate, but this revocation does not happen automatically. Manual activation is required, involving setting a specific registry flag and creating a scheduled task named Secure-Boot-Update. Instructions for this are buried deep on Microsoft's website, making it easy for administrators to miss. Although the certificate expired on October 19, 2026, this does not prevent vulnerable binaries from loading unless the certificate is explicitly blocklisted.

Attribution and Actor Methodology

The campaign has been attributed to APT41 with medium confidence. Key factors include PDB path identifiers matching those described in earlier ESET research on tools linked to the group. ESET said: "the community assumes to be related to APT41. This post describes a kernel implant with a PDB path starting with C:Users\xdd\Desktop" The identifier 'xdd' was observed multiple times in BlackX payloads. The use of DLL sideloading with encrypted files is also a common pattern among Chinese-speaking threat actors.

Security expert Georgy Kucherin noted that APT groups rarely borrow code from the cybercrime underground. Adapting a commercial crimeware tool like BlackLotus allows these sophisticated adversaries to bypass complex Windows boot protections without reinventing the wheel, establishing persistent and invisible control over high-value networks.

Defence and Patch Deployment Challenges

Kaspersky's endpoint protection in this instance blocked the malware's attempt to disable it, causing the attack to fail. Had it succeeded, attackers would have deployed spyware abusing legitimate cloud services to steal information. The research was presented at the Security Analyst Summit 2026.

Microsoft's plan mentions a future 'Enforcement Phase' that would automatically revoke the vulnerable certificate, but this stage had not been implemented at the time of discovery. This incident shows a critical patch management failure: updates alone are sometimes insufficient. Organisations must ensure their IT departments manually execute Microsoft's recommended steps to close the Baton Drop vulnerability and similar UEFI protection flaws.

Related coverage

More from Vulnerabilities