Rootkit
Stealth malware that hides itself deep in the OS.
What it is
A rootkit is malware designed to conceal its own presence and that of other tools, typically by hooking or modifying the operating system at the user or kernel level.
Why it matters
Because rootkits subvert the very APIs investigators rely on, they can hide processes and files from a live OS. Memory forensics finds them anyway, since it examines the memory image rather than trusting the compromised OS.
In practice
A kernel rootkit hiding a malicious driver that is invisible to the OS but plainly listed in a memory image.
What to look for
- Differences between what the system reports and what a raw read finds.
- Unsigned or unexpected drivers.
- Hooks in system call or API tables.
Common mistake
Trusting the live system's own tools to find it. Compare against offline disk analysis or a memory image.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Collection Plan
Build a host collection command list, ordered by volatility.
- Windows Host Case
An alert on a live Windows workstation: read the event logs and the Registry, rebuild the timeline, then decide what to collect.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Volatility 3 Open source
A widely used open source framework for analyzing memory images with plugins. Our notes.
-
Velociraptor Open source
Can collect memory and query live process memory across many hosts. Our notes.
-
CrowdStrike Falcon Commercial
EDR agents watch memory activity on the host, such as injection and unbacked code.
ATT&CK techniques
- T1014: Rootkit
Read next
- Memory Acquisition: Capturing a live system's RAM into an image for analysis.
- Process Hollowing: Malware starts a legit process, then swaps its guts for malicious code.
- Persistence: Mechanisms that keep attacker access across reboots.