competition-firmware-layout

Maps firmware image partitions, boot chains, and update flows to recover embedded secrets.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-firmware-layout-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-firmware-layout
Source: https://github.com/dbx0/skills/tree/main/skills/binary-re-pwn/reverse-engineering/competition-firmware-layout
Command: npx skills add https://github.com/dbx0/skills --skill competition-firmware-layout-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF firmware challenges often hide flags inside layered images, partition tables, and boot or update chains, and jumping straight to interesting files wastes time and corrupts evidence. This Skill provides a structured workflow for unpacking firmware, tracing how it boots and updates, and reducing the image to the smallest path that reaches the decisive artifact. ## Core Features & Use Cases - Image Layout Mapping: Identify containers, partition headers, compression, filesystems, and nested images while recording offsets, sizes, and hashes before extraction. - Boot and Update Chain Tracing: Follow control flow from bootloader to kernel to init to services, or from update package to verifier to installer, noting which credentials and configs each stage consumes. - Evidence Packaging: Keep pristine images, extracted layers, and patched copies separate while recording keys, signatures, and entrypoints in one compact evidence chain. - Use Case: Given a router firmware image in a CTF, map its partitions, trace the init scripts that load a hardcoded credential, and prove exactly where the boot flow consumes it to reach the flag. ## Quick Start After the ctf-sandbox-orchestrator has routed here, ask the assistant to unpack the firmware image, map its partition layout, and trace the boot chain to the flag artifact.

Frequently Asked Questions about competition-firmware-layout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unpack a firmware image in a CTF challenge?

Start by identifying the outer container, partition headers, compression, and filesystem type, then record offsets, sizes, and hashes before extracting anything. Separate bootloader, kernel, initramfs, rootfs, and config blobs into distinct layers for analysis.

How to trace a firmware boot chain to find credentials?

Map control flow from bootloader to kernel to init to services, noting which keys, certificates, passwords, or config files each stage consumes. The decisive secret is only proven when you show where the boot or update flow actually loads it.

When should I use this skill instead of a general reverse engineering skill?

Use it when the challenge centers on firmware structure, partitions, boot or update flows, and embedded configs. If the work shifts to native crash behavior or exploit primitives after extraction, switch back to the broader reverse engineering skill.

What evidence should I preserve during firmware analysis?

Keep partition offsets, hashes, filesystem types, mount paths, boot entrypoints, and update metadata together with extracted secrets and the stage that consumes them. Store original images, extracted layers, and patched copies as separate artifacts.

Why does firmware analysis fail when editing extracted files too early?

Editing extracted files before recording pristine offsets and hashes destroys the evidence chain linking secrets to the boot or update stage that consumes them. Always snapshot the original image and document boundaries before any modification.