<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apt41 on CuraSec</title><link>https://curasec.metacog.co.kr/tags/apt41/</link><description>Recent content in Apt41 on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 14:29:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/apt41/index.xml" rel="self" type="application/rss+xml"/><item><title>BlackX UEFI Bootkit Bypasses Secure Boot via Missing DBX Revocations</title><link>https://curasec.metacog.co.kr/insights/2026-10-24-blackx-uefi-bootkit-bypasses-secure-boot-on-patched-windows/</link><pubDate>Sat, 24 Oct 2026 14:29:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-24-blackx-uefi-bootkit-bypasses-secure-boot-on-patched-windows/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> The bypass exploits outdated UEFI Secure Boot revocation databases (DBX) rather than an unpatched flaw — audit all Windows endpoints and servers to confirm DBX revocation lists are current, and verify that UEFI firmware update policies include revocation database refresh.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> APT41&amp;rsquo;s deployment of a new UEFI-level bootkit warrants reviewing Kaspersky&amp;rsquo;s technical report for IOCs and ATT&amp;amp;CK mappings, then building or tuning detections for Secure Boot bypass behaviors (e.g., unexpected bootloader measurements, DBX modification events) in EDR and firmware telemetry.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A China-nexus group&amp;rsquo;s use of firmware-level persistence against diplomatic targets is a useful data point for risk posture discussions, but the campaign&amp;rsquo;s narrow targeting of Central Asian diplomatic entities means no immediate board-level action is required for most organizations.&lt;/li>
&lt;/ul></description></item></channel></rss>