CyberKit

Kernel Object

Also called Executive Object.

Kernel-managed structures like processes, files, and events.

What it is

A managed structure the Windows object manager tracks, such as a process, thread, file, event, or mutant, each with a header, type, and reference count. Handles in user mode ultimately refer to these objects.

Why it matters

Enumerating kernel objects from memory reveals what a system was actually doing (files open, synchronization primitives in use, processes alive) independent of potentially subverted APIs. Specific objects, like named mutants, double as malware indicators.

In practice

Listing kernel file objects from a memory image to find a handle to a staging directory that the malware kept open for exfiltration.

What to look for

  • Processes, threads, files and mutants tied to a suspect process.
  • Objects with names that match known malware.
  • Handles to objects in other processes.

Common mistake

Looking only at processes. Files, keys and mutants opened by a process often explain what it was doing.

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

  • Handle Table: A process's table of open references to kernel objects.
  • Kernel Pool: The kernel's heap, split into paged and nonpaged regions, for objects.
  • Mutant: A named synchronization object malware often uses as an infection marker.

Sources