What happened
Kaspersky’s analysis reveals that the BlackX bootkit loads before the operating system, bypassing Secure Boot on Windows machines that have not received the latest revocation list updates. The campaign, attributed to the China‑linked APT41 group, has focused on diplomatic entities in Tajikistan, Uzbekistan and Turkmenistan during early 2026.
Why it matters for trust and compliance
- The incident highlights a control gap in firmware integrity management; continuous evidence collection of Secure Boot status and revocation updates provides the defensible audit trail required across frameworks.
- Enable automated collection of Secure Boot and revocation‑list evidence to demonstrate control enforcement.
- Map firmware‑integrity controls to your governance framework, creating a reusable audit artifact.
Who is affected
Government & diplomatic ministries Enterprises using Windows endpoints with Secure Boot enabled
Recommended actions
- Automate deployment of the latest Secure Boot revocation lists across all Windows devices.
- Implement continuous firmware‑integrity monitoring and store immutable logs in a central Trust Center.