BlackX UEFI Bootkit Exploits Baton Drop in Central Asia APT Campaign

· Original article ↗

Summary

Kaspersky researchers detail BlackX, a BlackLotus-like UEFI bootkit used against diplomatic agencies in Central Asia. It exploits Baton Drop despite installed patches when certificate revocation is not activated; attribution to APT41 is medium confidence.

Key points

  • Kaspersky identified BlackX in an early 2026 campaign targeting diplomatic agencies in Tajikistan, Uzbekistan, and Turkmenistan.
  • Attackers reportedly gained administrator privileges before deploying BlackX, which exploits Baton Drop (CVE-2022-21894) to install custom Machine Owner Keys and load EFI files despite Secure Boot.
  • The researchers found the targeted machines were patched, but the Baton Drop mitigation requires manually activating certificate revocation; the automatic enforcement phase had not been implemented at publication.
  • BlackX delivers a kernel driver that tampers with security-solution callbacks and ETW providers, and protects bootkit files by returning a handle to calc.exe instead.
  • Two observed espionage payloads include a RAT using Google Drive, OneDrive, or Yandex.Disk for C2, and OxiDLLRunner, which launches a Rust payload communicating with www[.]archivetj[.]com.
  • Kaspersky assesses APT41 attribution with medium confidence, citing similarities to activity discussed in an ESET report and payload characteristics associated with Chinese-speaking actors.

Article Details

Attack Vectors
  • After compromising victim networks and obtaining administrator privileges, attackers deployed BlackX from an installer and an RC4-encrypted extensionless package.
  • BlackX exploits Baton Drop (CVE-2022-21894) to install custom Machine Owner Keys and load arbitrary EFI files, enabling manipulation of Secure Boot.
  • A bootkit-delivered payload is loaded through a legitimate executable abused via DLL sideloading.
  • A bootkit-delivered UEFI payload injects a malicious driver into the Windows kernel; the driver tampers with security callbacks and ETW providers.
  • The OxiDLLRunner DLL decrypts v8_context_snapshot.bin and launches shellcode followed by a Rust payload that communicates with a C2 server.
Defensive Notes
  • Ensure the Baton Drop patch is fully activated: installing the update alone does not automatically revoke the vulnerable signing certificate; the source says manual activation requires a registry flag and a scheduled task named Secure-Boot-Update.
  • Monitor Secure Boot revocation and enforcement status; the article reports that automatic enforcement had not yet been implemented at publication time.
  • Deploy security solutions across organizational machines and monitor the alerts they raise.
  • Kaspersky recommends its Exploit Prevention component as a measure against exploits when a patch is unapplied or no patch is available.

Indicators of compromise

TypeIndicatorContext
DOMAINwww[.]archivetj[.]comC2 server contacted by the Rust payload delivered through the bootkit.
MD5af8a983b9ada07eae1259bf2953abd40MD5 hash of jcef_helper.exe, the legitimate executable delivered by the bootkit and abused to load OxiDLLRunner.

MITRE ATT&CK

CVE

Threat Actors

Malware

Vendors

Products

Countries

Industries

Related Articles