A UEFI bootkit is malicious code that infects the Unified Extensible Firmware Interface firmware layer before the operating system starts. It can persist across disk reformats and may intercept boot flow, hide later malware, or weaken secure boot controls by running below normal endpoint defences.
How UEFI Bootkits Work
UEFI bootkits operate in the pre-OS trust boundary, which makes them different from ordinary user-space malware or even many kernel-level implants. Because they run before the operating system, they can tamper with the boot chain itself, shape what the OS sees at startup, and survive actions that would normally remove malware from disk.
This matters because the firmware layer is a high-trust foundation for secure boot, measured boot and device attestation. If that foundation is compromised, defenders may inherit a system that appears normal from inside the OS while its earliest execution path has already been altered.
Why UEFI Bootkits Are Hard To Remove
Persistence is the core problem. A bootkit can survive drive reimaging, operating system reinstallations and some recovery workflows because the malicious component sits outside the usual OS-managed storage and execution boundaries. That makes incident response more complicated than standard malware cleanup.
Bootkits also gain leverage from the fact that firmware compromise can undermine the very checks meant to stop it. A weak or bypassed secure boot chain can allow unsigned or altered code to execute early, and a compromised boot flow may hide later-stage payloads, making endpoint telemetry incomplete or misleading.
Detection And Exposure Checks
Exposure assessment starts with asset inventory and firmware visibility. Organisations need to know which systems use UEFI, which platforms have secure boot enabled, whether firmware and boot components are current, and whether any vendor advisories or revocation notices apply to the fleet. Without that inventory, the affected surface is easy to underestimate.
Detection is often indirect. Useful signals include secure boot state changes, unexpected bootloader modifications, boot-time integrity failures, attestation mismatches and other evidence that the chain of trust no longer matches the expected firmware baseline. In practice, the question is not just whether malware is present, but whether the device can still be trusted to report honestly from the first instruction onward.
Recovery, Hardening And Trust Rebuild
Remediation usually requires more than a normal malware cleanup. Organisations may need firmware reflash, boot component replacement, secure boot revocation updates or full hardware replacement when the platform cannot be trusted after compromise. The right path depends on whether the boot chain can be verified and restored to a known-good state.
Rebuilding trust also means protecting the adjacent controls that bootkits try to weaken. Measured boot, TPM-backed attestation, secure boot key hygiene and firmware update integrity all help restore confidence in the platform. For high-value systems, boot integrity should be treated as a continuous assurance problem, not a one-time setup task.
Risk and Threat Considerations
UEFI bootkits are dangerous because they sit below the operating system and can turn the startup process itself into an attacker-controlled persistence layer. That creates a severe exposure when defenders rely on endpoint tooling that only becomes active after the malicious code has already executed.
Failure mechanism: The attacker abuses firmware-level trust to preserve access, hide follow-on malware, or interfere with secure boot verification before the OS and its controls are fully operational.
Impact: The system may remain compromised across reinstallation, security tools may see an incomplete view of the host, and organisations can lose confidence in the device’s boot integrity until firmware is verified or replaced.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1542.003 — Pre-OS Boot: Bootkit | Defines bootkits as pre-OS persistence and execution technique. |
| Recommendation — Map boot-time artifacts to T1542.003 and hunt for pre-OS persistence and tampering. | ||
| NIST SP 800-53 Rev 5 | SI-7 — Software, Firmware, and Information Integrity | Directly addresses verifying firmware and boot integrity for this threat. |
| SI-7(9) — Verify Boot Process | Specifically covers verification of the boot process against alteration. | |
| IA-3 — Device Identification and Authentication | Boot-chain trust often depends on device-level authentication and attestation. | |
| Recommendation — Apply SI-7 to verify boot integrity and detect firmware tampering. Use SI-7(9) to validate the boot process and confirm trusted startup state. Apply IA-3 to bind device trust to verified platform identity signals. | ||
| CIS Controls v8 | 5 — Account Management | Supports recovery and access review after compromise when trust in the host is lost. |
| Recommendation — Use CIS-5 to review and revoke access tied to potentially compromised hosts. | ||
Practitioner Guidance
Why practitioners should care: Bootkits are a platform-integrity problem, not just a malware-removal problem. If you treat them like ordinary endpoint infections, you can miss the persistence mechanism and leave the device in a state that still cannot be trusted.
What to watch for: Prioritise systems with boot anomalies, unexpected secure boot changes, unexplained attestation failures or repeat reinfection after disk-level remediation. Those are the cases where firmware validation and stronger recovery actions matter most.
Practitioner takeaway: When a UEFI bootkit is suspected, the recovery decision should start with trust in the boot chain, not with the OS image.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org