Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label bootkit malware attack. Show all posts

APT41 Linked to BlackX Bootkit Attacks on Central Asian Diplomatic Agencies

 

Cybersecurity researchers have uncovered an espionage campaign, believed to be conducted by APT41, targeting diplomatic organisations in Tajikistan, Uzbekistan and Turkmenistan. This used a malicious UEFI bootkit called BlackX which is similar to previously seen BlackLotus bootkit. The malware exploits a vulnerability within Microsoft’s Secure Boot. 

This was discovered during an investigation into attacks targeting diplomatic agencies in early 2026. Researchers believe that APT41 conducted this due to similarities with previous campaigns, and similarities in how the malware was developed. BlackLotus initially became known in 2022 when it was put up for sale on a hacking forum for $5000. In 2023 ESET confirmed that BlackLotus could bypass Secure Boot by exploiting the Baton Drop vulnerability (CVE-2022-21894). 

Although Microsoft have released patches for this, researchers have found that BlackX can still exploit this vulnerability. Before installing BlackX attackers had gained administrator rights. The instalation tool downloads encrypted elements from another file, making it more difficult to identify the malicious files. BlackX exploits the Baton Drop vulnerability to install custom Machine Owner Keys. This allows the attackers to run unauthorised EFI components. 

Once installed BlackX injects a malicious driver into the Windows kernel. The driver will disrupt security tools by disabling callback functions. It will also modify Event Tracing for Windows providers. The driver will attempt to hide the files by intercepting open requests to return a handle which relates to the Windows Calculator application. Researchers have identified two other pieces of espionage malware. 

The first piece is a remote access trojan which uses Google Drive, Microsoft OneDrive or Yandex Disk for C2 communications. This can be used to control the device by sending commands, running .NET code and uploading/downloading files. The second malware piece is called OxiDLLRunner. This uses obfuscated code to run a Rust component which communicates with the C2 server (www[.]archivetj[.]com). This can be used to send malicious DLL files and run the exported functions. BlackX has been linked to APT41 as a previous report mentioned a kernel implant and potential UEFI bootkit. 
The malware also contains the ‘xdd’ marker within the components. The code has also been obfuscated in a way commonly seen with Chinese speaking threat actors. Although these factors have been identified there is uncertainty around this. Investigation found that it was possible to infect the devices due to the mitigation for Baton Drop in Microsoft requiring manual intervention. This involves setting a registry flag and creating a scheduled task. The automatic mitigation to disable the certificate has not been implemented. 

This shows the importance of ensuring that your security mitigations are fully in place. You should check your Secure Boot protections are in place, monitor your security alerts and ensure you have endpoint protection in place which can detect any attempts to exploit.

Microsoft Patches Critical Secure Boot Flaw Enabling Bootkit Malware Attacks on Most PCs

 

Microsoft has addressed a critical vulnerability in Secure Boot that could be exploited by attackers to disable security protections and deploy persistent bootkit malware across a wide range of systems.

The flaw, uncovered by cybersecurity firm Binarly, involved a legitimate BIOS update utility signed with Microsoft’s UEFI CA 2011 certificate. This certificate is pivotal in the UEFI Secure Boot process, ensuring only trusted bootloaders and low-level software run during startup.

According to Binarly, the utility is trusted on most modern devices using UEFI firmware. However, a significant issue arose due to the utility’s ability to access a user-writable NVRAM variable without adequate validation. “This means an attacker with administrative privileges could manipulate the variable and write arbitrary data during the boot process,” the researchers explained.

By exploiting the vulnerability, Binarly demonstrated that Secure Boot could be deactivated, allowing any unsigned UEFI code to execute. This opens the door for stealthy bootkit malware that persists even after hard drive replacements. The affected module had been active since 2022 and was uploaded to VirusTotal in 2024 before being disclosed to Microsoft in February 2025.

The flaw has been formally logged as CVE-2025-3052 with a high severity score of 8.2 out of 10. Microsoft included the fix in its June 2025 Patch Tuesday update, addressing this and other newly discovered issues.

"During the triage process, Microsoft determined that the issue did not affect just a single module as initially believed, but actually 14 different modules," Binarly said. "For this reason, the updated dbx released during the Patch Tuesday on June 10, 2025 contains 14 new hashes."

With all affected modules now patched, Microsoft has significantly reduced the risk of attackers using this Secure Boot vulnerability to compromise system integrity.