CyberKit

Direct Kernel Object Manipulation

Also called DKOM.

Editing in-memory kernel structures to hide processes or drivers.

What it is

A rootkit technique that alters live kernel structures directly, for example unlinking an EPROCESS from the active-process list, so the object still exists and runs but no longer appears in the lists the OS enumerates. It manipulates data rather than hooking code.

Why it matters

DKOM defeats tools that trust OS-maintained lists, which is exactly why memory forensics leans on signature-based scanning to find objects the manipulation tried to hide. The discrepancy between a scan and the linked list is itself a strong detection signal.

In practice

A process invisible to the live task list but recovered by pool-tag scanning, its forward and backward list pointers rewritten to splice it out.

What to look for

  • Processes found by scanning but not by list walking.
  • Drivers present in memory but missing from the loaded module list.
  • Token privileges changed without matching events.

Common mistake

Using one plugin to list processes. Compare list walking with pool scanning to catch unlinked objects.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

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

  • Pool Tag Scanning: Finding kernel objects by their fixed pool allocation tags.
  • EPROCESS: The kernel structure describing a running Windows process.
  • Kernel Object: Kernel-managed structures like processes, files, and events.

Sources