CyberKit

Static Analysis

Also called Static malware analysis.

Examining a sample's code and structure without executing it.

What it is

The practice of inspecting a file's bytes, headers, strings, and disassembled code without running it. It ranges from quick triage of metadata to full reverse engineering of the program logic.

Why it matters

Static review is safe to perform on any host and can surface capabilities, embedded indicators, and packing before detonation. It is the first lens most analysts apply, and it guides how much deeper dynamic work a sample warrants.

In practice

Pulling readable strings and the import table from a suspicious binary to decide it is a downloader before ever running it.

What to look for

  • File type, hashes, imports and strings.
  • Compiler artifacts, packer signatures and section entropy.
  • Embedded resources or configs.

Common mistake

Concluding a file is benign because strings look clean. Packing hides the real code from static views.

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.

  • 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 Analysis: Running a sample under observation to record what it actually does.
  • Disassembly: Translating machine code back into human-readable assembly.
  • Import Address Table: The table the loader fills with addresses of imported functions.

Sources