CyberKit

Reflective DLL Loading

Also called Reflective Loading, Manual Mapping.

Loading a DLL from memory while bypassing the OS loader and its lists.

What it is

A technique where code maps a DLL into a process directly from a memory buffer, performing relocation and import resolution itself instead of calling the normal loader. Because the OS loader is bypassed, the module never appears in the loaded-module lists.

Why it matters

Reflectively loaded modules run without touching disk and without registering in the loader's lists, so they evade module-walking tools and demand region-based hunting in memory. Executable regions whose contents parse as a PE but are not in any module list are the giveaway.

In practice

Finding PE headers inside a private memory region of a process whose loaded-module list omitted any such DLL, the signature of a reflectively loaded implant.

What to look for

  • PE headers in memory regions that are not backed by a file.
  • Executable private memory with an MZ header.
  • No image load events for the module.

Common mistake

Searching disk for the DLL. It was mapped from memory and may never touch disk.

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

Sources