Course contentsShow
← Security
Lesson 1549 of 3,05231. Operating System Security - MalwareFree lesson

Direct Kernel Object Manipulation (DKOM)

Modifying kernel data structures directly to hide processes from task lists without hooking APIs.

Direct Kernel Object Manipulation (DKOM)

You'll learn how kernel-mode rootkits can hide processes by directly editing internal kernel data structures, bypassing all API-level detection.

What Is DKOM?

Direct Kernel Object Manipulation is a rootkit technique that modifies kernel data structures directly in memory, without hooking system calls or APIs. Instead of intercepting function calls like System Call Hooking does, DKOM simply rewrites the data that the kernel itself uses to track processes, threads, drivers, and other system objects.

Think of it like this: System Call Hooking is like intercepting phone calls to lie about who's in the building. DKOM is like erasing someone's name directly from the building's master directory — no one even tries to call them because they don't "exist" in the records.

How DKOM Works

The Windows kernel maintains linked lists and other data structures to track active processes (EPROCESS structures). Each process points to the next in a doubly-linked list. A DKOM rootkit:

  1. Locates its own process structure in kernel memory
  2. Modifies the linked list pointers to "unlink" itself
  3. The previous process now points directly to the next process, skipping over the hidden one

From the kernel's perspective, the hidden process simply doesn't exist in the active process list. Task Manager, Process Explorer, and even security tools querying the kernel will not see it — they're reading the legitimate (but modified) kernel data.

Why It's Dangerous

DKOM operates at the lowest level possible, manipulating the kernel's "ground truth." Since it doesn't hook functions, traditional detection methods that look for API hooks fail completely. The hidden process can continue running, communicating, and performing malicious activities while remaining invisible to most monitoring tools.

Key Takeaway: DKOM hides malware by directly editing the kernel's internal data structures, making processes invisible without ever hooking a single API call — a stealthy technique that bypasses hook-based detection mechanisms.