CyberKit

Memory-Mapped File

Also called Section Object, File Mapping.

A file whose contents are mapped into a process's address space.

What it is

A file or pagefile-backed range projected into virtual memory through a section object, so a process accesses its contents as if they were ordinary memory. Executable images and shared memory are commonly implemented this way.

Why it matters

Mapped files let an examiner recover the actual in-memory contents of executables and data files, which may differ from the on-disk copy after unpacking or tampering. Comparing a mapped image against its disk file is how process-replacement and patching are detected.

In practice

Dumping the mapped image of a running process and finding its in-memory code diverged from the on-disk binary, exposing a hollowed-out process.

What to look for

  • Mapped files from temp or unusual folders.
  • Mapped images whose file on disk has changed.
  • Sections without a backing file name.

Common mistake

Assuming the mapped file still exists. It may have been deleted while still loaded.

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