Skip to main content
Mallory
Malware5 associated CVEs

BlackLotus

Tracked since Dec 3, 2025 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days21 mentions · peak 8 in a dayToday
Vulns5Associated
Actors0Associated
ATT&CK46Techniques
IOCs23Tracked
Type
Bootkit
Capabilities
PersistencePost exploitationDefense evasionProcess injectionReconnaissance
Platforms
Windows

BlackLotus is a Windows UEFI bootkit advertised on cybercrime forums in late 2022 and publicly confirmed in 2023 as the first documented in-the-wild UEFI bootkit capable of bypassing Secure Boot on fully updated Windows 11 systems. It exploits the Baton Drop vulnerability, CVE-2022-21894, using older, legitimately signed Windows boot managers that remain trusted unless the necessary Secure Boot revocations are applied. Installation requires preexisting administrative privileges or physical access; BlackLotus serves as a post-compromise persistence and defense-evasion mechanism rather than an initial-access vector.

BlackLotus places malicious boot components in the EFI System Partition and establishes persistence by enrolling an attacker-controlled Machine Owner Key. Its components execute before Windows loads, enabling interference with operating-system security controls. The bootkit disables hypervisor-protected code integrity, BitLocker protection, and Microsoft Defender Antivirus. It deploys a malicious kernel driver that protects its boot files against deletion or tampering and installs a user-mode HTTP downloader. The downloader is injected into a Windows system process and supports command-and-control communications, retrieval of additional payloads, and network discovery.

Its persistence resides in disk-based boot components rather than requiring an implant in motherboard firmware. Remediation requires cleaning or rebuilding the EFI System Partition as well as the operating-system partition. Preventive protection depends on appropriate boot-manager updates and Secure Boot trust revocations, not merely patching the original vulnerability.

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

5 CVEs 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). | In 2023, malware tracked as BlackLotus became the first publicly documented in-the-wild UEFI bootkit capable of bypassing Secure Boot on fully updated Windows 11 systems.View vulnerability →Source ↗
CVE-2023-24932via the hacker newsSecure Boot Bypass in Microsoft Windows Boot ManagerThe Slovakian cybersecurity company said it also found "limited indications" that some versions of the backdoor may feature a UEFI bootkit component likely exploiting CVE‑2023‑24932, another security feature bypass vulnerability linked to BlackLotus. | BlackX is assessed to be an updated version of BlackLotus, a notorious bootkit that was first observed being advertised on cybercrime forums in late 2022.View vulnerability →Source ↗
CVE-2026-8863via infosecurity magazine newsUEFI Secure Boot Bypass in Microsoft-Signed Legacy Shim BootloadersTwo CVE IDs, CVE-2026-8863 and CVE-2026-10797, cover the reported shims, and Microsoft revoked the vulnerable binaries in the dbx update shipped with its June 9 Patch Tuesday.View vulnerability →Source ↗
CVE-2026-10797via infosecurity magazine newsUEFI Secure Boot revocation bypass in legacy shimTwo CVE IDs, CVE-2026-8863 and CVE-2026-10797, cover the reported shims, and Microsoft revoked the vulnerable binaries in the dbx update shipped with its June 9 Patch Tuesday.View vulnerability →Source ↗
CVE-2024-7344via codebyUEFI Secure Boot bypass in Howyar ReloaderЧерез такой вектор можно развернуть полноценные UEFI-буткиты - BlackLotus или Bootkitty - даже при включённом Secure Boot. | CVE-2024-7344, обнаруженная исследователем ESET Martin Smolár, затрагивает UEFI-приложение Reloader - компонент нескольких утилит восстановления: Howyar SysReturn, Greenware GreenGuard, Radix SmartRecovery, Sanfong EZ-back System, CES NeoImpact. По данным ESET, также затронуты WASAY eRecoveryRX и SignalComputer HDD King.View vulnerability →Source ↗
MITRE ATT&CK

Techniques & procedures

46 distinct techniques documented for this family, organized by ATT&CK tactic.

Resource Development

2 techniques
T1587.002Code Signing CertificatesEvidence1

“Some BlackLotus samples are signed with self-signed certificate.”

T1588.005ExploitsEvidence1

“a Proof of Concept (PoC) exploit… publicly available… developer has likely just adapted the available PoC…”

Initial Access

1 technique
T1195Supply Chain CompromiseEvidence1

PKfail is a firmware supply-chain security issue affecting major device vendors and hundreds of device models. PKfail is the result of shipping default test keys included by IBVs in their reference implementation

Execution

5 techniques
T1106Native APIEvidence1

“uses various native Windows APIs… In some cases, a direct syscall instruction invocation is used…”

T1129Shared ModulesEvidence1

“HTTP downloader can load and execute DLLs received from the C&C server.”

T1203Exploitation for Client ExecutionEvidence1

“It exploits… CVE-2022-21894… to bypass UEFI Secure Boot… exploitation is still possible as the affected, validly signed binaries have still not been added to the UEFI revocation list… brings its own copies of legitimate – but vulnerable – binaries…”

T1559Inter-Process CommunicationEvidence1

“capable of communicating… by using a named Event and Section… Names… generated based on… MAC address.”

T1574Hijack Execution FlowEvidence2

The routines responsible for installing the hook chain (start with ImgArchStartBootApplication ) are very similar as shown in the figure. BlackLotus trampoline code modification logic to setup hooks is identical to Umap code on GitHub.

Persistence

8 techniques
T1037Boot or Logon Initialization ScriptsEvidence1

The first in-the-wild UEFI bootkit bypassing UEFI Secure Boot on fully updated UEFI systems is now a reality. Once the persistence is configured, the BlackLotus bootkit is executed on every system start.

T1037.001Logon Script (Windows)Evidence1

Based on function similarity, we detect the replacement of bootmgfw.efi with the shim.

T1112Modify RegistryEvidence1

“to disable this feature, the installer sets the Enabled registry value under the HypervisorEnforcedCodeIntegrity registry key to zero.”

T1542Pre-OS BootEvidence5

Bootkits are a type of malware that infects the boot process of a computer, allowing attackers to gain persistent access and control over the system.

T1542.001System FirmwareEvidence14

Attackers could bypass UEFI Secure Boot on a wide range of systems thanks to 11 Microsoft-signed UEFI shim bootloaders carrying vulnerabilities that have remained buried for more than a decade... Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits ... even with Secure Boot switched on.

T1542.003BootkitEvidence19

Bootkits usually targeted MBR/ESP in the early 2010s, but as the cost of firmware attack decreased rapidly, the modern bootkits started to target DXE or even PEI.

T1543.003Windows ServiceEvidence1

sc.exe create blacklotus_driver.sys binPath=C:\windows\temp\blacklotus_driver.sys type=kernel && sc.exe start blacklotus_driver.sys

T1547.001Registry Run Keys / Startup FolderEvidence3

The most well-known real-world example is BlackLotus, a UEFI bootkit discovered in 2023 that exploited vulnerabilities in older Windows bootloaders (CVE-2022-21894 and CVE-2023-24932) to bypass Secure Boot on fully updated Windows 11 systems.

Privilege Escalation

9 techniques
T1037Boot or Logon Initialization ScriptsEvidence1

The first in-the-wild UEFI bootkit bypassing UEFI Secure Boot on fully updated UEFI systems is now a reality. Once the persistence is configured, the BlackLotus bootkit is executed on every system start.

T1037.001Logon Script (Windows)Evidence1

Based on function similarity, we detect the replacement of bootmgfw.efi with the shim.

T1055.002Portable Executable InjectionEvidence1

“When… winlogon.exe process has started, it injects and executes… the HTTP downloader – into it.”

T1055.012Process HollowingEvidence1

“In the case of executing files directly in memory, svchost.exe is used as an injection target.”

T1068Exploitation for Privilege EscalationEvidence5

Since Secure Boot bypass attacks cross security boundaries or allow the disabling of security features, we need to treat them as privilege escalation vulnerabilities to more accurately reflect the CVSS impact score.

T1134.002Create Process with TokenEvidence1

“can use WTSQueryUserToken and CreateProcessAsUserW to execute downloaded payloads… with local system privileges.”

T1543.003Windows ServiceEvidence1

sc.exe create blacklotus_driver.sys binPath=C:\windows\temp\blacklotus_driver.sys type=kernel && sc.exe start blacklotus_driver.sys

T1547.001Registry Run Keys / Startup FolderEvidence3

The most well-known real-world example is BlackLotus, a UEFI bootkit discovered in 2023 that exploited vulnerabilities in older Windows bootloaders (CVE-2022-21894 and CVE-2023-24932) to bypass Secure Boot on fully updated Windows 11 systems.

T1548.002Bypass User Account ControlEvidence1

“If it’s not the case, it tries to elevate… using the UAC bypass method… UAC bypass via Program Compatibility assistant.”

Stealth

17 techniques
T1014RootkitEvidence3

MITRE ATT&CK catalogs the technique as T1014 under defense evasion.

T1027Obfuscated Files or InformationEvidence1

“Almost all embedded strings… are encrypted… embedded files… encrypted using 256-bit AES… some… compressed using LZMS.”

T1027.007Dynamic API ResolutionEvidence1

“APIs… resolved exclusively during runtime and function hashes instead of function names are used…”

T1036.005Match Legitimate Resource Name or LocationEvidence1

“hide its files… by using legitimate filenames, such as grubx64.efi… or bootmgfw.efi …”

T1055.002Portable Executable InjectionEvidence1

“When… winlogon.exe process has started, it injects and executes… the HTTP downloader – into it.”

T1055.012Process HollowingEvidence1

“In the case of executing files directly in memory, svchost.exe is used as an injection target.”

T1070.004File DeletionEvidence1

“installer registers itself to be deleted… after… exploitation… removes traces… by deleting all files included in exploitation chain…”

T1070.009Clear PersistenceEvidence1

“‘uninstall’ command… removing all bootkit files from the ESP and restoring original… Boot Manager.”

T1134.002Create Process with TokenEvidence1

“can use WTSQueryUserToken and CreateProcessAsUserW to execute downloaded payloads… with local system privileges.”

T1211Exploitation for StealthEvidence4

there are "limited indications" suggesting the involvement of a UEFI bootkit, likely exploiting CVE-2023-24932 ... a security feature bypass vulnerability in the Windows Boot Manager

T1218System Binary Proxy ExecutionEvidence1

BlackLotus takes advantage of this, bringing its own copies of legitimate – but vulnerable – binaries to the system in order to exploit the vulnerability...

T1497.001System ChecksEvidence2

Certain BlackLotus installation packages, as analyzed by ESET, refrain from carrying out the installation of the bootkit in case the affected host employs regional settings associated with Armenia, Belarus, Kazakhstan, Moldova, Russia, or Ukraine.

T1542Pre-OS BootEvidence5

Bootkits are a type of malware that infects the boot process of a computer, allowing attackers to gain persistent access and control over the system.

T1542.001System FirmwareEvidence14

Attackers could bypass UEFI Secure Boot on a wide range of systems thanks to 11 Microsoft-signed UEFI shim bootloaders carrying vulnerabilities that have remained buried for more than a decade... Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits ... even with Secure Boot switched on.

T1542.003BootkitEvidence19

Bootkits usually targeted MBR/ESP in the early 2010s, but as the cost of firmware attack decreased rapidly, the modern bootkits started to target DXE or even PEI.

T1574Hijack Execution FlowEvidence2

The routines responsible for installing the hook chain (start with ImgArchStartBootApplication ) are very similar as shown in the figure. BlackLotus trampoline code modification logic to setup hooks is identical to Umap code on GitHub.

T1622Debugger EvasionEvidence1

“contains various anti-VM, anti-debug… The HTTP downloader won’t be deployed if a kernel debugger is detected…”

Defense Impairment

6 techniques
T1112Modify RegistryEvidence1

“to disable this feature, the installer sets the Enabled registry value under the HypervisorEnforcedCodeIntegrity registry key to zero.”

T1553Subvert Trust ControlsEvidence4

With the modified MokList variable, an attacker can easily load any self-signed shim bootloader, which is actually another vulnerability in the chain used to keep secure boot active.

T1553.001Gatekeeper BypassEvidence1

The first in-the-wild UEFI bootkit bypassing UEFI Secure Boot on fully updated UEFI systems is now a reality.

T1553.002Code SigningEvidence4

Secure Boot is a UEFI firmware feature that checks the digital signature of every piece of software trying to load before Windows boots... If a bootloader’s signature doesn’t match what Secure Boot trusts, the firmware refuses to run it.

T1553.006Code Signing Policy ModificationEvidence1

По MITRE ATT&CK это одновременно Bootkit (T1542.003) для persistence и Code Signing Policy Modification (T1553.006) для defense evasion - Secure Boot формально включён, но фактически удалось его обойти.

T1685Disable or Modify ToolsEvidence7

A device stuck on the 2011 KEK can only receive DBX updates signed with that key, and the ability to sign on it ended June 24... Losing DBX updates means losing this kind of protection against whatever comes next.

Discovery

6 techniques
T1016System Network Configuration DiscoveryEvidence1

“determine the public IP… by requesting api.ipify[.]org service.”

T1016.001Internet Connection DiscoveryEvidence1

“checks the internet connection by querying… www.msftncsi[.]com/ncsi[.]txt”

T1082System Information DiscoveryEvidence1

“beacon… containing… IP… OS… Edition… CPU… GPU… RAM… SecureBoot…”

T1497.001System ChecksEvidence2

Certain BlackLotus installation packages, as analyzed by ESET, refrain from carrying out the installation of the bootkit in case the affected host employs regional settings associated with Armenia, Belarus, Kazakhstan, Moldova, Russia, or Ukraine.

T1614System Location DiscoveryEvidence1

“installers… do not proceed… if… locales… ro-MD… ru-RU… uk-UA… be-BY… hy-AM… kk-KZ”

T1622Debugger EvasionEvidence1

“contains various anti-VM, anti-debug… The HTTP downloader won’t be deployed if a kernel debugger is detected…”

Command and Control

6 techniques
T1071Application Layer ProtocolEvidence1

It also deploys an HTTP downloader that enables communication with the Command and Control server and has the ability to load further user-mode or kernel-mode payloads.

T1071.001Web ProtocolsEvidence2

...an HTTP downloader that communicates with a command-and-control (C2) server to retrieve additional user-mode or kernel-mode malware... the latter is capable of executing commands received from the C2 server over HTTPS.

T1105Ingress Tool TransferEvidence2

It also deploys an HTTP downloader that enables communication with the Command and Control server and has the ability to load further user-mode or kernel-mode payloads.

T1132.001Standard EncodingEvidence1

“then URL-safe base64 encoded.”

T1573.001Symmetric CryptographyEvidence1

“data… is decrypted using 256-bit AES in CBC mode with… HWID string used as the key.”

T1573.002Asymmetric CryptographyEvidence1

“data is first encrypted using an embedded RSA key, then URL-safe base64 encoded.”

Indicators of compromise

Observables

23 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

85 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 TechnicaDiscussed as historical background for BlackX. BlackLotus exploited Baton Drop using older vulnerable Windows boot managers whose signing certificate remained trusted despite a vulnerability patch. It bypassed Secure Boot, executed malicious code before Windows and many defenses were fully operational, and loaded a malicious kernel-mode driver.Read more ↗xakepNews · Oct 28, 2026Критическую уязвимость в UEFI случайно раскрыли раньше срока - ХакерBootkit mentioned as background in a discussion of earlier UEFI security problems. The article does not connect BlackLotus to exploitation of CVE-2026-97631 or describe its capabilities.Read more ↗the hacker newsNews · Oct 28, 2026Critical 16-Year-Old UEFI Flaw Can Run Code Before Secure Boot on Network-Booting ServersReferenced as a Secure Boot bypass in a comparison of remediation requirements. The article does not associate BlackLotus with exploitation of the reported EDK II vulnerability.Read more ↗xakepNews · Oct 27, 2026UEFI-буткит BlackX использует уязвимость Baton Drop для обхода Secure Boot - ХакерUEFI bootkit first advertised on criminal forums in 2022 for $5,000. ESET confirmed in 2023 that it could bypass Secure Boot through Baton Drop. Discussed as a technical predecessor or relative of BlackX: researchers believe BlackX's developers reverse-engineered BlackLotus or obtained its source code. Some shared code was absent from the incomplete BlackLotus source leak published in 2023.Read more ↗
+74 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 matching23Match every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities5CVEs 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 mapping46Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.