CuraSec

tag: Secure-Boot · 2 items

2026-10-24 · The Hacker News · source ↗ #uefi-bootkit#apt41#secure-boot
  • Engineer — Plan: 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.
  • SOC/IR — Plan: APT41’s deployment of a new UEFI-level bootkit warrants reviewing Kaspersky’s technical report for IOCs and ATT&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.
  • Leader — Learn: A China-nexus group’s use of firmware-level persistence against diplomatic targets is a useful data point for risk posture discussions, but the campaign’s narrow targeting of Central Asian diplomatic entities means no immediate board-level action is required for most organizations.
2026-07-15 · The Hacker News · source ↗ #uefi#secure-boot#firmware
  • Engineer — Plan: No active exploitation or PoC yet, but these are legitimately signed shims that could be weaponized for UEFI bootkit deployment — audit your systems’ Secure Boot allowlists and verify no deprecated shim binaries are present in your boot chain.
  • SOC/IR — Learn: UEFI bootkit delivery via trusted-but-vulnerable signed shims is a useful persistence vector to understand; no exploitation is occurring now and no IOCs or detection guidance are available yet, but worth filing against future UEFI anomaly detection work.
  • Leader — Skip