What is Rootkit?
A rootkit is malware built to hide itself and other malicious components from the operating system and security tools, usually by intercepting the system calls that list files, processes, registry keys and network connections. Running with administrator, kernel or firmware-level privileges, it lets an attacker keep covert access to a compromised host.
Definition
- Rootkit
- A rootkit is malware built to hide itself and other malicious components from the operating system and security tools, usually by intercepting the system calls that list files, processes, registry keys and network connections. Running with administrator, kernel or firmware-level privileges, it lets an attacker keep covert access to a compromised host.
How Rootkit Works
NIST describes a rootkit as a set of tools an attacker uses after gaining root-level access, to conceal their activity and keep that access through covert means. The defining feature is concealment, not damage. MITRE ATT&CK's technique T1014 describes the mechanism: they hide programs, files, network connections, services and drivers by intercepting or hooking the operating system API calls that supply that information. A tool that asks the system for a process list gets an answer with the malicious process already removed.
Where the implant lives decides how hard it is to see.
- User-mode variants hook functions inside processes; MITRE lists Hildegard, which modified
/etc/ld.so.preloadon Linux to overridereaddir()so its files vanish from directory listings. - Kernel-mode variants load as drivers or kernel modules and tamper with the structures the kernel itself uses, which defeats any tool running above them; Drovorub used a Linux kernel module to hide processes, files and network artifacts.
- Below that sit bootkits and firmware implants such as LoJax, the UEFI implant MITRE attributes to APT28. A firmware implant lives in flash memory on the motherboard, so reinstalling the operating system does not remove it.
Modern Windows makes kernel-level hiding harder but not impossible. Microsoft's documentation on securing the boot process starts from exactly this threat: because they run in kernel mode and can start before the operating system, they can hide completely. Secure Boot, Trusted Boot and Early Launch Anti-Malware check the boot chain and early drivers before the rest of the system loads. Attackers answer by loading legitimately signed but vulnerable drivers to reach the kernel, a pattern known as bring your own vulnerable driver.
Rootkit in SOC Operations
The hard part of this triage is that the infected host may lie to you. If the EDR agent and a live response tool on the same machine disagree, or a connection seen in firewall or flow data has no matching process on the host, treat the host's own view as untrusted. Useful signals come from outside or below the operating system: Sysmon event ID 6 (driver loaded) for unsigned or rarely seen drivers, a known vulnerable driver being loaded, new kernel services, Secure Boot or measured boot attestation failures, and network sessions that nothing visible on the host accounts for. For a confirmed kernel or firmware implant, cleaning is not a realistic goal. Preserve memory and disk for forensics, rebuild from known-good media, and reflash firmware if the evidence points there.
Practice Rootkit in a Real SOC
SOCSimulator provides hands-on training with realistic SIEM, XDR, and Firewall interfaces. Build real analyst skills investigating rootkit scenarios with zero consequences, free.
Frequently Asked Questions
- How do you know if you have a rootkit?
- Usually not from the infected machine itself, since hiding is its job. Clues include security tools that crash or get disabled, network traffic no visible process explains, drivers nobody can account for, and differences between what the host reports and what an offline scan or memory image shows. A scan from boot media or a memory capture analyzed elsewhere is more trustworthy than any tool running inside the suspect system.
- What is the difference between a virus and a rootkit?
- A virus is defined by how it spreads, by infecting other files. A rootkit is defined by what it does once installed: hide. They describe different things, so one piece of malware can be both, and many rootkits are installed by a Trojan or by an attacker who already has administrator rights rather than by any self-spreading code.
- What is an example of a rootkit?
- MITRE ATT&CK lists several under technique T1014: LoJax, a UEFI firmware implant used by APT28; Drovorub, a Linux kernel module that hides processes, files and network artifacts; and Hildegard, which hijacks /etc/ld.so.preload so its files disappear from directory listings. Together they cover firmware, kernel and user mode.
- How do I get rid of a rootkit?
- For anything beyond a simple user-mode case, rebuild the machine instead of trying to clean it. Capture memory and disk first if you need evidence, then wipe and reinstall from trusted media, and reflash the firmware if a bootkit or UEFI implant is suspected. Rotate every credential used on the host, because this kind of implant almost always means the attacker had administrator access.
Sources
Related Terms
Persistence is the set of techniques an adversary uses to keep access to a compromised system after ...
Privilege escalation is an attacker gaining rights they were never given, after they already have a ...
EDR (endpoint detection and response) is security software that puts an agent on each laptop, server...
Digital forensics is the scientific process of collecting, preserving, analyzing, and presenting dig...
An advanced persistent threat (APT) is a well-resourced adversary, often state-backed, that picks a ...
Fileless malware is malicious code that runs in memory through tools the operating system already tr...
More Threats Terms
Related SOC Training Resources
Threat Hunter Career Guide: Salary & Skills
Threat Hunters do not wait for alerts. You develop hypotheses based on threat intelligence and adversary behavior models…
Read more Career PathIncident Responder Career Guide: Salary & Skills
Incident Responders lead the technical response when confirmed breaches happen. You coordinate containment, run forensic…
Read more Career PathSOC Analyst (Tier 2) Career Guide: Salary & Skills
Tier 2 SOC Analysts handle the investigations that Tier 1 escalates. You dig into multi-stage attacks, coordinate contai…
Read more ComparisonSOCSimulator vs Hack The Box: Comparison
Different tools for different career paths. SOCSimulator trains defensive analysts. Hack The Box trains offensive securi…
Read more ToolXDR Training Console: SOCSimulator
The XDR console in SOCSimulator replicates the investigation workflow of platforms like CrowdStrike Falcon, Microsoft De…
Read more TechniqueMITRE ATT&CK® Techniques: Detection Training Library
Browse all MITRE ATT&CK® techniques with detection strategies and example alerts.
Read more Career PathCybersecurity Career Paths: 2026 Guide
Explore SOC analyst career paths with salary data, required skills, and certification roadmaps.
Read more PlaybookSOC Investigation Playbooks: Step-by-Step Guides
Practitioner investigation playbooks with decision trees and real SIEM queries.
Read more FeatureShift Mode: Real-Time SOC Simulation
Practice alert triage under realistic time pressure with SLA timers and noise injection.
Read more FeatureOperations: Guided Training Operations
Structured CTF-style investigation operations covering real-world attack scenarios.
Read more BlogSOCSimulator Blog: Security Training Insights
Articles on SOC analyst skills, detection engineering, and career development.
Read more FeatureSOCSimulator Pricing: Free Plan Available
Compare free and Pro tiers.
Read more