Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A rootkit is a type of malware designed to gain privileged access to a system and hide its own presence, along with other malicious activity, from users and security tools.

What Is a Rootkit?
A rootkit is a type of malware built to keep privileged, hidden access to a computer. The name comes from Unix, where “root” is the most powerful account and a “kit” was the set of tools an intruder installed to stay in control. A rootkit’s defining feature is concealment: it modifies the system so that files, processes, network connections, and registry entries belonging to the attacker simply do not appear.
Rootkits rarely act alone. They are usually installed after an attacker has already gained administrator rights, often through privilege escalation, and they protect other malware, such as backdoors and credential stealers, from discovery.
Operating systems answer questions like “which processes are running?” through layers of functions. A rootkit inserts itself into one of those layers and edits the answers. When a security tool asks for a list of files, the rootkit removes its own entries before the list is returned. Common techniques include hooking system calls, modifying kernel data structures directly (known as direct kernel object manipulation), and filtering driver output.
The deeper the rootkit sits, the harder it is to find, because tools running above it receive falsified information.
| Type | Where it runs | Notes |
|---|---|---|
| User-mode | Inside applications and system libraries | Easiest to build and to detect |
| Kernel-mode | Inside the operating system kernel, usually as a driver | Full control, can hide from most tools |
| Bootkit | In the boot process, before the operating system loads | Survives reinstalls of some components |
| Firmware or UEFI | In system firmware on the motherboard or devices | Survives disk replacement and full OS reinstall |
| Hypervisor | Beneath the operating system as a virtual machine layer | Largely theoretical, rarely seen in the wild |
Rootkits have made headlines for decades. In 2005, Sony BMG music CDs installed copy protection software that used rootkit techniques to hide itself on Windows PCs, creating a vulnerability that other malware then abused. In 2018, researchers identified LoJax, the first known UEFI rootkit used in the wild, attributed to the Russian group APT28. In 2023, the BlackLotus bootkit was found able to bypass Secure Boot on fully updated Windows 11 systems by exploiting a vulnerability (CVE-2022-21894). Attackers also increasingly use “bring your own vulnerable driver” techniques, loading a legitimate but flawed signed driver to gain kernel access and disable security tools.
Because rootkits lie to the system, detection relies on finding inconsistencies or looking from outside the compromised layer:
Modern platforms have made rootkits much harder to install:
Careful system hardening ensures these protections are actually switched on, which is not always the case on older or customised builds.
Once a kernel or firmware rootkit is confirmed, the affected system can no longer be trusted to report on itself. The safest response is usually to preserve evidence through memory and disk imaging, then rebuild the system from known-good media, and in the case of firmware rootkits, reflash or replace the firmware. All credentials used on the machine should be treated as compromised.
At Privia Security, our Digital Forensic Services use memory and disk forensics to uncover hidden malware and determine exactly what an attacker did.
Traditional antivirus can detect many known user-mode rootkits, but kernel and firmware rootkits are designed to hide from tools running on the infected system. Modern endpoint detection, offline scanning from trusted media, memory forensics, and boot integrity checks are much more effective, especially when combined with protections that stop rootkits from loading in the first place.
A clean reinstall removes user-mode and most kernel-mode rootkits, but not all bootkits and certainly not firmware or UEFI rootkits, which live outside the disk. Those may require reflashing firmware or even replacing hardware. Before reinstalling, preserve forensic evidence so that you can understand how the attacker got in.
A bootkit is a rootkit that infects the boot process, such as the master boot record or UEFI boot components, so that it runs before the operating system and its security tools. This early position gives it great control. Secure Boot, measured boot, and timely firmware and operating system updates are the main defences against bootkits.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.