IRP Hooking
Also called IRP Major Function Hooking, Driver Dispatch Hooking.
Hooking a driver's I/O request handlers to intercept device traffic.
What it is
A technique that overwrites the I/O request packet dispatch routine pointers in a driver object, so requests to that device or file-system stack pass through attacker code. The hooked function-table entries point away from the owning driver's image.
Why it matters
IRP hooks let malware tamper with file, disk, or network I/O at the driver layer, hiding or altering data as it flows through the stack. Driver dispatch entries that resolve outside the driver's own module are a clear hooking indicator in a memory image.
In practice
A file-system filter driver's read dispatch pointer redirected into a hidden module that stripped malicious files from directory results.
What to look for
- Driver major function pointers that point into another driver.
- Hooks on file system or network drivers.
- Unsigned drivers loaded near the time of the hook.
Common mistake
Assuming every redirected handler is hostile. Filter drivers from security tools do this legitimately.
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.
Read next
- System Service Dispatch Table Hooking: Redirecting system-call entries to attacker code in the kernel.
- Interrupt Descriptor Table Hooking: Hijacking interrupt handlers by editing the IDT in memory.
- Kernel Object: Kernel-managed structures like processes, files, and events.