CyberKit

API Hashing

Also called Function name hashing.

Referring to functions by hash to hide which APIs malware uses.

What it is

A form of dynamic resolution where malware identifies the functions it wants by a precomputed hash of each name rather than the name itself. At runtime it hashes export names and matches against its constants.

Why it matters

Because the readable API names never appear, this defeats string- and import-based triage and obscures intent until the hashes are reversed. Matching the hashing algorithm to a constant is a routine reversing exercise.

In practice

Recognizing a known ROR-13 name-hashing routine, then mapping the sample's hash constants back to the APIs it actually calls.

What to look for

  • Hash constants compared in a loop over export names.
  • Known algorithms such as ROR13.
  • No readable API names in the binary.

Common mistake

Guessing APIs by hand. Hash lookup databases and scripts resolve them quickly.

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

  • Dynamic API Resolution: Looking up needed functions at runtime instead of importing them.
  • Shellcode: Compact, self-contained machine code that runs from an injected buffer.
  • String Analysis: Extracting readable text from a binary to infer its purpose.

Sources