About 80% of malware in the wild targets Windows. If you analyze malware professionally, you will eventually hit a wall where your tools stop explaining why something works. That wall is Windows internals knowledge, and this book is how you climb it.
What This Book Is (and Is Not)
Windows Internals by Mark Russinovich, David Solomon, and Alex Ionescu is not a malware analysis book. It is a 1,500+ page, two-volume deep dive into how Windows actually works at the kernel level: processes, memory, I/O, security, networking, and the registry.
The reason it matters for malware analysis: every technique that malware uses (process injection, token manipulation, rootkit hooking, registry persistence) exploits a documented Windows mechanism. This book documents those mechanisms.
The Chapters That Matter Most for Malware Analysis
You do not need to read all 1,500 pages. Here is a prioritized reading guide:
Must-read (Part 1)
| Chapter | Topic | Why it matters |
|---|---|---|
| Processes & Threads | EPROCESS, ETHREAD, job objects | Understand process hollowing, injection, and how tools like Process Explorer work |
| Memory Management | Virtual memory, page tables, memory-mapped files | Essential for memory forensics with Volatility |
| Security | Tokens, ACLs, privileges, integrity levels, UAC | Explains privilege escalation, token theft, and why some malware needs admin |
Read when needed (Part 2)
| Chapter | Topic | When to read |
|---|---|---|
| I/O System | Drivers, IRPs | When analyzing rootkits or malicious drivers |
| Networking | Winsock, TDI, NDIS | When reverse engineering C2 communication |
| Registry | Internal structure, hive format | When investigating persistence mechanisms |
How to Actually Apply It
Reading about EPROCESS structures is useless if you do not connect it to real analysis. Here is how to bridge theory and practice:
1. Process hollowing (CreateProcess + WriteProcessMemory)
The book explains how CreateProcess builds the EPROCESS structure and maps the executable. Malware creates a process in suspended state, unmaps the original image, writes its payload, and resumes. Knowing the internal sequence tells you exactly where to set breakpoints in a debugger.
2. Token manipulation
Chapter on Security explains access tokens, impersonation levels, and privilege constants. When you see malware calling AdjustTokenPrivileges or DuplicateTokenEx, the book tells you what those tokens contain and what the attacker gains.
3. Memory forensics
The Memory Management chapter maps directly to Volatility plugins. Understanding VADs (Virtual Address Descriptors) and PTE (Page Table Entries) makes Volatility output meaningful instead of just rows of hex.
Sysinternals: The Companion Toolkit
Russinovich created Sysinternals. The book frequently references these tools, and they are your daily drivers for dynamic analysis:
Process Explorer → Live process tree, DLL list, handles
Process Monitor → Real-time file/registry/network activity
Autoruns → Persistence mechanisms across 30+ locations
TCPView → Active network connections per process
Handle → Open handles (files, registry keys, mutexes)
These tools are the practical application layer of the book. If the book explains how Windows manages processes, Process Explorer lets you see it happening.
The Honest Downsides
- It is dense. Some chapters read like kernel source documentation. Take breaks.
- No malware examples. You have to make the connections yourself. Pair it with Practical Malware Analysis for the applied side.
- Two volumes, expensive. The 7th edition covers Windows 10/11, which is what you want.
Verdict
If you are serious about malware analysis on Windows, this book is not optional. It is the difference between knowing what malware does and understanding why it works. Read Part 1 first, keep Part 2 as a reference, and use Sysinternals daily.
Pair it with Practical Malware Analysis for the hands-on complement.
Originally published at MalwareIntel. MalwareIntel is a free threat intelligence platform monitoring 13 public CTI sources.
Free resources:
- Defense Kit — Sigma + YARA + IOCs per malware family
- Detection Gap Analyzer — Check your MITRE ATT&CK coverage
- CTI Assessment — Rate your threat intel maturity in 5 min
Top comments (0)