A bootkit is a type of malware designed to infect a computer’s boot process and gain deep, persistent control before the operating system even starts. Bootkits are especially dangerous because they can hide from traditional security tools and remain on a system even after reboots or reinstallations.
Read on to find out exactly what a bootkit is, what it does, how it impacts organizations, practical steps for prevention, and expert strategies for removal.
A bootkit is a stealthy strain of malware that infects the part of a computer used to start (or "boot up") the operating system. Unlike most malware, which infects files within the operating system itself, a bootkit targets the earliest phase of a system’s startup process—for example, the Master Boot Record (MBR), Volume Boot Record (VBR), or newer Unified Extensible Firmware Interface (UEFI) firmware. By striking so early, a bootkit can run code before security software loads, giving an attacker high-level privileges and nearly undetectable persistence.
Bootkits are part of a broader category called rootkits. Think of rootkits as tools for attackers to maintain privileged, covert access to a system; a bootkit is a rootkit that specializes in hijacking the boot process.
For security pros, this means a bootkit is not just malware. It’s a badge of an adversary who is aiming for the deepest, most stubborn compromise.
The main purpose of a bootkit is persistence and stealth. Here’s what attackers gain:
Pre-OS execution: Bootkit code activates before the operating system, bypassing many defenses.
Deep control: Hijacks system controls, installs backdoors, or disables security measures.
Evasion: Remains hidden from most endpoint detection tools, which only scan after OS startup.
Enabler: Often used as a beachhead for more malware, data theft, or even total system takeover.
For an organization, a bootkit infection isn’t just a malware alert; it could signal an advanced persistent threat, espionage attempts, or a precursor to further compromise.
Targeting low-level system components: Bootkits aim for the MBR, VBR, or UEFI partitions, which are required for system startup.
Modifying boot code or firmware: They add malicious code into these startup areas.
Trigger on every reboot: Because they launch before the OS, bootkits can load malicious drivers, manipulate kernel operations, hide their presence, or open backdoors before the system’s usual protections even activate.
Surviving reinstalls: Since some bootkits live outside the typical hard-drive partitions (e.g., in UEFI firmware), simple system resets or OS reinstallations might not remove them.
This is why traditional antivirus tools can struggle with detection.
A bootkit infection poses extensive risks, including:
Data theft: Stealing credentials, sensitive files, and intellectual property—often undetected for long periods.
Full system compromise: Attackers can gain admin-level access, alter system settings, and run additional malware.
System instability: Random crashes, blue screens, failed OS boots, or unexplained system changes.
Long-term persistence: The bootkit can survive many efforts to clean or reimage the computer unless specialized removal steps are taken.
Supply chain attacks: Some bootkits have targeted firmware updates or vendor tools, spreading through trusted sources.
For a business, the presence of a bootkit could mean regulatory issues, lost data, crippled operations, and a longer (and costlier) incident response process.
Prevention requires a layered, proactive approach:
Enable Secure Boot: UEFI Secure Boot checks signatures of all boot software and only runs trusted code (learn more from NIST).
Keep firmware and OS updated: Apply all updates from trusted sources, as many patches address boot process vulnerabilities.
Use endpoint protection with firmware scanning: Choose security tools that can scan the MBR, VBR, and UEFI areas—not just the OS.
Avoid untrusted media: Don't boot from unknown USB drives, CDs, or downloads. Attackers often use removable media to spread bootkits.
Monitor for suspicious activity: Watch for failed boots, system errors, or changes to boot sequences. Anomalies could be early signs of trouble.
Limit admin access: Only allow trusted staff to update or modify boot, firmware, or UEFI settings.
Building a culture of security awareness is crucial. Remind teams that “plug and play” with random media is a classic entry point for advanced malware.
Removing a bootkit is a lot tougher than dealing with typical malware. Here’s how the pros do it:
Isolate the affected system: Pull the device off the network to prevent further spread.
Use specialized boot repair tools: Tools that can wipe and restore the MBR, VBR, or UEFI are essential. Many standard virus scanners cannot reach this deep.
Firmware reflash or update: For UEFI-based infections, updating or re-flashing the firmware may be necessary.
Re-image with trusted media: Always perform a clean install from a known-good source. Don’t trust recovery partitions, as these could also be compromised.
Check removable storage: Bootkits can hide on USB sticks and external drives.
Re-enable protections: After cleaning, make sure Secure Boot and other protections are turned on.
If you’re an enterprise IT team, this is one time you might want to call for outside incident response help (for example, from a trusted partner or your country’s cyber agency).
```
User inserts malicious USB or boots compromised device
↓
Bootkit infects MBR/VBR/UEFI before OS loads
↓
Bootkit hides itself, disables security protections
↓
Attacker gains persistence, can launch more malware
↓
Victim experiences instability or data theft, usually months after infection
```
The LoJax bootkit, discovered in 2018, targeted UEFI firmware and was used in advanced espionage campaigns. LoJax was able to survive system wipes and reinstalls, and required firmware refLashing to completely remove the infection (US-CERT LoJax reference).
Bootkits are advanced malware that infect a system’s startup process for deep access and persistence. The purpose of a bootkit is to avoid detection, gain control, and enable further system compromise. Bootkits can have severe impacts on both individuals and organizations, including data theft, operational disruption, and regulatory exposure. To prevent bootkit malware, enable Secure Boot, keep systems patched, use advanced endpoint protection, avoid untrusted media, and monitor for odd activity. Removing bootkits requires specialized tools and sometimes professional help. Don’t rely on basic antivirus alone.
