CyberKit

Import Address Table

Also called IAT.

The table the loader fills with addresses of imported functions.

What it is

The Import Address Table is the part of a PE that the Windows loader populates with the resolved addresses of functions a program imports from external libraries. Calls to those APIs route through this table.

Why it matters

The IAT is a fast read on a sample's capabilities (networking, crypto, injection), and is a prime target for inline hooks and reconstruction after unpacking. A sparse or empty IAT often signals dynamic API resolution to hide intent.

In practice

Rebuilding the IAT of a memory-dumped, unpacked sample so its API calls become legible for analysis.

What to look for

  • Imports such as VirtualAlloc, WriteProcessMemory and CreateRemoteThread.
  • Very few imports, a sign of packing or runtime resolution.
  • GetProcAddress and LoadLibrary used to fetch the rest.

Common mistake

Concluding a sample is harmless from a short import list. It may resolve everything 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