CyberKit

Indicator Extraction from Memory

Also called String Extraction, Memory Triage.

Pulling addresses, names, and strings from RAM to drive a hunt.

What it is

The practice of harvesting observable artifacts (remote addresses, file paths, mutant names, URLs, and strings) from a memory image so they can be used to scope an incident. It turns raw memory contents into searchable indicators.

Why it matters

Indicators recovered from memory often surface activity that left nothing on disk, then seed sweeps across an environment to find other affected hosts. It bridges a single memory analysis to enterprise-wide detection and scoping.

In practice

Extracting a command-and-control address and a mutant name from one host's memory image, then sweeping the fleet for both to find every infected machine.

What to look for

  • Hashes, domains, IPs, file paths and mutex names.
  • Indicators that are shared infrastructure, such as CDNs.
  • Context on how each indicator was observed.

Common mistake

Blocking every extracted domain. Some are legitimate services the malware abused.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • MISP Open source

    An open source platform for storing, correlating and sharing threat indicators.

  • OpenCTI Open source

    Organizes intelligence as linked STIX objects, from actors down to indicators.

  • VirusTotal Commercial

    Pivots between files, domains and IPs to find related infrastructure.

  • ATT&CK Navigator Open source

    Shows a group's known techniques on the ATT&CK matrix.

Read next

Sources