BlackX UEFI Bootkit Exploits Baton Drop to Bypass Secure Boot

· Original article ↗

Summary

Kaspersky researchers detail BlackX, a UEFI bootkit used in an early-2026 espionage campaign targeting Central Asian diplomatic agencies. It exploited Baton Drop to bypass Secure Boot; the report describes its security-disabling driver, espionage payloads and manual-rev

Key points

  • BlackX was discovered in an early-2026 espionage campaign targeting diplomatic agencies in Tajikistan, Uzbekistan and Turkmenistan.
  • The operation was attributed to APT41 with medium confidence.
  • Researchers say BlackX exploits Baton Drop (CVE-2022-21894), using a method similar to BlackLotus to enroll custom Machine Owner Keys and load arbitrary EFI files.
  • BlackX's kernel driver can disable security processes and registry callbacks and tamper with Event Tracing for Windows providers.
  • The bootkit deploys a RAT that uses Google Drive, OneDrive or Yandex.Disk for command-and-control, as well as OxiDLLRunner, which launches shellcode and a Rust payload.
  • Kaspersky says victims had fully patched Windows, but the relevant Secure Boot certificate revocation had not been manually activated.
  • Researchers suggest BlackX was derived from reverse-engineering BlackLotus or obtaining its source code; they found code in BlackX samples that was absent from the public leak.

Article Details

Attack Vectors
  • BlackX exploited Baton Drop (CVE-2022-21894) to bypass Secure Boot, enroll custom Machine Owner Keys, and load arbitrary EFI files.
  • The bootkit loaded a malicious Windows kernel driver signed with a now-revoked certificate. The driver disabled security-related processes and registry callbacks and tampered with ETW providers.
  • OxiDLLRunner was sideloaded by googleupdate.exe; it decrypted v8_context_snapshot.bin to launch shellcode and a Rust payload.
  • The Rust payload retrieved DLL plugins from archivetj[.]com and executed their create_plugin functions.
  • A RAT used Google Drive, OneDrive, or Yandex.Disk for command and control and to upload and download files.
Defensive Notes
  • Installing the Baton Drop patch does not automatically revoke the vulnerable “Windows Production PCA 2011” certificate; administrators must trigger the revocation manually.
  • Kaspersky researchers warn that the certificate’s October 19, 2026 expiration does not prevent vulnerable binaries from loading unless administrators add the certificate to a blocklist.
  • Kaspersky reported that the victims were running fully patched Windows releases, but the bootkit succeeded because the additional Secure Boot revocations had not been activated.

Indicators of compromise

TypeIndicatorContext
DOMAINarchivetj[.]comDomain from which the BlackX payload retrieved DLL plugins.

MITRE ATT&CK

CVE

Threat Actors

Malware

Vendors

Products

Countries

Related Articles