Skip to main content
Mallory
Malware2 associated actors1 associated CVE

BlackX

Tracked since Oct 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days31 mentions · peak 9 in a dayToday
Vulns1Associated
Actors2Associated
ATT&CK0Techniques
IOCs4Tracked
Type
Bootkit
Capabilities
PersistenceDefense evasionPost exploitation
Platforms
Windows

BlackX is a UEFI bootkit targeting Windows systems, discovered by Kaspersky researchers during an early-2026 cyberespionage campaign against diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan. Attackers deploy it after compromising victim networks and obtaining administrator privileges. It provides boot-level persistence and defense evasion rather than serving as an initial-access mechanism.

BlackX exploits Baton Drop (CVE-2022-21894) to bypass Secure Boot and enroll attacker-controlled Machine Owner Keys, allowing malicious EFI components to execute before Windows starts. Its exploitation chain closely resembles BlackLotus, but it uses a different kernel driver and subsequent payloads. Observed victims had installed relevant Windows updates but lacked the additional Secure Boot revocations needed to prevent vulnerable signed boot components from loading. The installer keeps its components and strings in a separate encrypted package, complicating recovery and analysis.

The bootkit loads a signed malicious Windows kernel driver that attempts to disable security-related process, thread, and registry callbacks and interfere with Event Tracing for Windows. It conceals bootkit files by redirecting file-open requests to a legitimate Windows executable. Some product-specific interference routines were ineffective during testing. The driver also deploys user-mode espionage payloads, including a remote-access Trojan supporting additional .NET code, file transfers, and cloud-service command and control through Google Drive, OneDrive, or Yandex Disk. Another observed payload, OxiDLLRunner, uses DLL sideloading to launch a Rust component capable of receiving and executing additional DLL plugins.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Associated CVEs

Associated vulnerabilities

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.

CVE-2022-21894via arstechnica securityExploited in the wildBaton DropBoth BlackLotus and BlackX exploit “Baton Drop,” a logic flaw in the Windows boot manager that allows attackers to bypass Secure Boot (and, under certain conditions, extract BitLocker encryption keys). | The organizations infected by the new bootkit, which is tracked under the name BlackX, had installed all of these patches.View vulnerability →Source ↗
Threat actors

Associated threat actors

2 distinct threat actors Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
APT41

Эксперты «Лаборатории Касперского» обнаружили новый UEFI-буткит BlackX, который использовался в атаках на дипломатические ведомства Таджикистана, Узбекистана и Туркменистана.

via xakepxakep.ru
Earth Lusca

The new implant, named BlackX, targeted diplomatic organizations in Tajikistan, Uzbekistan, and Turkmenistan.

via tech timestechtimes.com
Indicators of compromise

Observables

4 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Activity feed

Recent activity

32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
arstechnica securityNews · Nov 3, 2026UEFI bootkit infected fully patched Windows machines. Is Microsoft to blame? - Ars TechnicaUEFI bootkit that exploits the Windows boot manager's Baton Drop vulnerability to bypass Secure Boot. It infected organizations that had installed the referenced Microsoft vulnerability fixes and subsequent trust-revocation updates. The excerpt does not explain how BlackX overcame those mitigations.Read more ↗scworldNews · Oct 29, 2026Podcast Segment: Vulnpocalypse Continues Until Defense Improves - PSW #950 | SC MediaBlackX bypasses Secure Boot on patched Windows systems that lack the required revocations. It undermines Windows startup defenses and third-party security solutions while maintaining long-term, covert access to compromised devices. Successful deployment requires administrator privileges or physical access to the target host.Read more ↗xakepNews · Oct 27, 2026UEFI-буткит BlackX использует уязвимость Baton Drop для обхода Secure Boot - ХакерUEFI bootkit deployed after attackers obtain initial access and administrator privileges. Exploits Baton Drop to bypass Secure Boot and establish pre-Windows persistence. Installs a malicious kernel driver that suppresses security callbacks and ETW telemetry, protects bootkit files by redirecting access to calc.exe, and deploys espionage payloads. Fully updated systems remain exposed when administrators have not manually activated the required certificate revocation. Researchers attribute the campaign to APT41 with medium confidence.Read more ↗cryptika blogNews · Oct 27, 2026Hackers Revive BlackLotus Techniques to Bypass Windows Secure Boot and Deploy Malware | Cryptika CybersecurityPost-compromise bootkit deployed after attackers obtain administrator privileges. It exploits Baton Drop to manipulate the boot trust chain and install custom Machine Owner Keys, allowing attacker-controlled EFI files to load. It injects a signed malicious kernel driver that attempts to suppress security monitoring and conceal bootkit files, then delivers espionage payloads. Fully patched systems remained exposed where vulnerable signed boot components had not been revoked. Researchers linked the campaign to APT41 with medium confidence; attribution and BlackX's authorship remain unconfirmed.Read more ↗
+12 more in the timeline. Sign up to see them
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching4Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors2Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities1CVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mappingEvery documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.