Skip to content
NewA calmer, faster ZeroHour
Threat actorhighExploited in the wild

Suspected APT41 uses BlackX bootkit against Central Asian diplomats

Original title: Suspected Chinese APT41 Hackers Use BlackX Bootkit to Bypass Windows Secure Boot

GBHackersby Mayura Kathir ()2 min read1 · 1 read
Part of a story covered by 5 sourcesBlackX bootkit bypasses Secure Boot at Central Asian diplomatsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Kaspersky says BlackX abuses unrevoked CVE-2022-21894 components on patched Windows when Secure Boot DBX updates are not applied.

Kaspersky says a UEFI bootkit it calls BlackX was deployed against diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan after network compromise and administrator access. Researchers attribute the operation to APT41 with medium confidence. The installer uses Baton Drop (CVE-2022-21894) to enroll attacker Machine Owner Keys, then a signed driver and user-mode payloads, including a cloud-storage RAT and OxiDLLRunner. Microsoft's Secure Boot revocations are not on by default; applying them without prepared replacements can stop systems from booting.

Unconfirmed: APT41 attribution is medium confidence, and the link to ESET's FishMonger bootkit notes remains inferential.

Key facts
  • BlackX resembles BlackLotus; a development link is not confirmed.
  • The kernel driver certificate, issued to a Wenjiang studio, was later revoked.
  • One payload uses Google Drive, OneDrive, or Yandex.Disk for command and control.
  • OxiDLLRunner sideloads through a renamed googleupdate.exe and contacts archivetj.com.
  • Administrators must update DBX and revoke Windows Production PCA 2011 after testing.
Security assessment · AI, from the articleExploited in the wild

Impact: UEFI persistence, kernel driver, and remote access after admin compromise

ProductAffected
Microsoft Windows Secure BootFully patched systems if bootloader revocations are not activated
What to do
  1. 1.Validate Secure Boot revocation status and follow Microsoft's staged DBX guidance.
  2. 2.Update recovery media and test boot compatibility before revoking Windows Production PCA 2011.
  3. 3.Treat inst.exe and the extensionless container PVMDIJGKAX2 as installation artifacts.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2022-21894
Secure Boot Security Feature Bypass Vulnerability
4.47%

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
domainwww.archivetj.comn to expose shellcode and a Rust payload communicating with www[.]archivetj[.]com. Downloaded DLL plugins export create_plugin and execut

From the original article

2 min read at gbhackers.com

Suspected Chinese APT41 hackers have deployed BlackX, a UEFI bootkit, against diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan. Researchers attribute the operation to APT41 with medium confidence. BlackX closely resembles BlackLotus, the bootkit advertised on underground forums for $5,000 in October 2022.

GBHackers

By Mayura Kathir · gbhackers.com

Read the full article at GBHackers

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.