BlackLotus bootkit bypasses UEFI Secure Boot on patched Windows 11

The developers of the BlackLotus UEFI bootkit have improved the malware with Secure Boot bypass capabilities that allow it to infected even fully patched Windows 11 systems.

BlackLotus is the first public example of UEFI malware that can avoid the Secure Boot mechanism, thus being able to disable security protections that come with the operating system.

The malware could be used to impair the BitLocker data protection feature, the Microsoft Defender Antivirus, and the Hypervisor-protected Code Integrity (HVCI) – also known as the Memory Integrity feature that protects against attempts to exploit the Windows Kernel.

The Unified Extensible Firmware Interface (UEFI) is the software that connects the operating system with the hardware that runs it.

It is low-level code that executes when the computer powers up and dictates the booting sequence before the operating system starts any of its routines.

BlackLotus commodity bootkit

The BlackLotus UEFI malware  promoted on hacking forums with a feature set that makes it virtually invisible to antivirus agents installed on the compromised host.

BlakLotus bootkit promoted on a hacker forum

The advertiser said that the malware takes only 80kb after installation and the cost of a license was $5,000, although rebuilds were available for just $200.

In a report this week, security researchers at ESET confirmed that the malware functions exactly as advertised and it can bypass the Secure Boot mechanism by leveraging a vulnerability from last year tracked as .

More information about why the security updates for CVE-2022-21894 don’t block this malware is available below.

Their investigation started from an HTTP downloader that turned out to be the BlackLotus UEFI bootkit user-mode component, which communicates with the command and control (C2) server and can load other payloads (user/kernel-mode).

BlackLotus infection chain

ESET malware researcher  notes that the attack starts with executing an installer that deploys the bootkit’s files to the EFI system partition, disables the HVCI and BitLocker protections, and reboots the host.

The attacker relies on legitimate binaries vulnerable to CVE-2022-21894 (Windows Hypervisor Loader, Windows Boot Manager, PE binaries) and their custom Boot Configuration Data (BCD).

Persistence on machines with UEFI Secure Boot enabled is achieved after the initial reboot by exploiting CVE-2022-21894 and enrolling the attacker’s Machine Owner Key (MOK).

The self-signed UEFI bootkit is launched after another reboot and the malicious kernel driver and the HTTP downloader are deployed to complete the malware installation.

BlackLotus execution flow
BlackLotus execution flow
source: ESET

Among the artifacts discovered in the BlackLotus code there are references to the Higurashi When They Cry anime series, including the names of two components and the issuer of the self-signed certificate for the bootkit binary.

Another reference the author of BlackLotus left in the malware code is in unused strings that decrypt into messages to Polish malware analyst .

References in BlackLotus bootkit code
References in BlackLotus bootkit code
source: ESET

Bug patched, security risk persists

ESET says that the BlackLotus installer can be either online or offline, the difference between them is that the offline variants carry the vulnerable Windows binaries.

The online version of the installer downloads the Windows binaries “directly from the Microsoft symbol store.”

The researchers saw the three files below being abused by the bootkit:


Smolár explains that  is what enables BlackLotus to bypass Secure Boot and  after disabling  (to load unsigned kernel code) and  (to allow modifying the boot chain without triggering the recovery procedure on systems with the Trusted Platform Module (TPM) hardware component):

  1. Exploiting CVE-2022-21894 to allow bypassing Secure Boot and installing the bootkit. Arbitrary code can then be executed in early boot phases, where the platform is still owned by firmware and UEFI Boot Services functions are still available. This allows attackers to do many things that they should not be able to do on a machine with UEFI Secure Boot enabled without having physical access to it, such as modifying Boot-services-only NVRAM variables. And this is what attackers take advantage of to set up persistence for the bootkit in the next step.
  2. Setting persistence by writing its own MOK to the MokList, Boot-services-only NVRAM variable. By doing this, it can use a legitimate Microsoft-signed shim for loading its self-signed (signed by the private key belonging to the key written to MokList) UEFI bootkit instead of exploiting the vulnerability on every boot.

To note, proof of concept (PoC)  has been publicly available for more than half a year, since August 2022. However, the security issue has been largely ignored.

Microsoft addressing the vulnerability in June 2022 was not enough to close the security gap because the UEFI DBX () has yet to be updated with the untrusted keys and binary hashes used in booting systems that have Secure Boot enabled.

“As a result, attackers can bring their own copies of vulnerable binaries to their victims’ machines to exploit this vulnerability and bypass Secure Boot on up-to-date UEFI systems” – 

Last year, researchers disclosed multiple UEFI vulnerabilities [, ] that could also be leveraged to disable Secure Boot. However, some of them can still be exploited due to vendors no longer supporting affected devices, incorrect patching, or not patching at all.

Smolár says that these failures were bound to attract the attention of a threat actor and lead to the creation of a highly-capable UEFI bootkit.

UEFI malware

UEFI bootkits are at the opposite end of run-of-the-mill malware. They are rare findings seen in attacks attributed to advanced threat actors working on behalf of a nation-state.

Although proof-of-concept bootkits have existed since 2013 (e.g. ) and malicious EFI bootloaders that prevented the machine from booting were found in 2020, the list of full-blown bootkits used in real-world attacks is incredibly short:

  •  – part of the homonymous surveillance toolset (a.k.a. FinFisher, WingBird)
  •  – a patched Windows Boot Manager on the EFI (Extensible Firmware Interface) system partition
  •  – a UEFI threat that hid in the firmware images of ASUS and Gigabyte motherboards to deploy a kernel-level implant every time the compromised Windows machine booted

The records for the larger category of UEFI malware, which also includes rootkits or firmware implants, is not much larger.

In 2018 ESET exposed the used by the Russian hackers in the APT28 group (Sednit/Fancy Bear/Sofacy).

Two years later, Kaskpersky published a report about the  rootkit that served Chinese-speaking hackers in data theft and espionage operations in 2019.

In early 2022, another UEFI firmware implant was disclosed.  was attributed to the Chinese-speaking group APT41/Winnti.

However, BlackLotus is the first ever publicly disclosed UEFI bootkit that bypasses Secure Boot and is associated with the cybercriminal world.