CyberKit

Dynamic API Resolution

Also called Runtime API resolution.

Looking up needed functions at runtime instead of importing them.

What it is

A technique where malware resolves the addresses of the functions it needs while running (typically by walking loaded modules and matching names or hashes) rather than declaring them in the import table.

Why it matters

It strips the import table of telltale APIs, blunting static capability assessment and import-based signatures. An almost-empty import table paired with module-walking code is a strong indicator of this evasion.

In practice

A sample importing only a couple of generic functions, then resolving its injection and crypto APIs by hash at runtime.

What to look for

  • LoadLibrary and GetProcAddress calls in loops.
  • Walking the PEB to find loaded modules.
  • Very few static imports.

Common mistake

Reading only the import table. The real API use shows up at runtime.

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.

  • Ghidra Open source

    A disassembler and decompiler for reading what a sample's code actually does. Our notes.

  • YARA Open source

    Writes rules that match a family's code or strings across many files. Our notes.

  • VirusTotal Commercial

    Shows how many engines flag a file, plus its relations to domains and other samples.

  • ANY.RUN Commercial

    An interactive sandbox where you watch a sample run and click through what it asks for.

Read next

Sources