1 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This is a Windows driver that detects kernel memory drivers and hidden threads, useful for rootkit developers to improve their evasion techniques. It implements several analysis methods, such as NMI callbacks and APC stack walks, to identify suspicious activity. You need to enable test signing and debugging to run it.
If you do, here's more
The article presents unKover, a Windows anti-rootkit driver designed to detect kernel memory drivers and hidden threads. It's a tool aimed at rootkit developers, allowing them to refine their evasion techniques while providing insights into detection methods. The tool is lightweight and focuses on minimizing false positives when identifying common driver mapper and rootkit combinations.
unKover employs several technical strategies for detection. It uses Non-Maskable Interrupts (NMIs) to analyze call stacks across cores, checking for pointers to unbacked memory. It also performs similar checks using Asynchronous Procedure Calls (APCs) for threads. The tool scans system threads and driver objects to ensure their memory addresses are valid and compares the in-memory .text sections of drivers to their on-disk counterparts, which can identify driver tampering. Other techniques include detecting threads removed from the PspCidTable and identifying hooked Major Function Handlers that point to unbacked memory.
To use unKover, users need to enable test signing and debugging for the kernel. Detailed commands are provided for setting this up, including using `sc.exe` to load and start the driver. There's a note about borrowing some code from another GitHub project focused on driver hijacking, pointing to a collaborative nature in developing these tools. The overall goal is to provide a practical resource for those interested in the nuances of rootkit development and detection.
Questions about this article
No questions yet.