CyberKit

PE Section

Also called Section header.

A named region of a PE holding code, data, or resources.

What it is

A PE section is a contiguous block of an executable, named by a section header, that holds a category of content such as code, initialized data, or resources. The section table records each one's size, location, and permissions.

Why it matters

Section names, permissions, and entropy are quick triage signals: oddly named, writable-and-executable, or high-entropy sections often flag packing or injected payloads. Mismatched raw and virtual sizes hint at runtime unpacking.

In practice

A PE carrying a writable, executable section with near-maximum entropy: a textbook sign of a packed payload.

What to look for

  • Sections with high entropy or unusual names.
  • Sections both writable and executable.
  • Raw size much smaller than virtual size, a sign of unpacking at runtime.

Common mistake

Judging by section name. Names are cosmetic; look at permissions, size and entropy.

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