re-firmware

Orchestrates firmware extraction, rootfs analysis, emulation, and hardware interface workflows for embedded devices.

64|9|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/dslsdzc/rev-skills --skill re-firmware-dslsdzc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: re-firmware
Source: https://github.com/dslsdzc/rev-skills/tree/main/.claude/skills/re-firmware
Command: npx skills add https://github.com/dslsdzc/rev-skills --skill re-firmware-dslsdzc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analyzing firmware and embedded devices requires coordinating many specialized steps—unpacking vendor images, mounting root filesystems, emulating binaries, and interfacing with physical hardware—and doing them in the wrong order wastes time or damages equipment. This gateway skill routes each firmware analysis task to the correct atomic skill in the correct sequence. ## Core Features & Use Cases - Guided Workflow: Orchestrates the full pipeline from triage (architecture/endianness detection) through extraction (binwalk/unblob), rootfs analysis, QEMU emulation, and hardware I/O (JTAG/UART/flash). - Decision Tree Routing: Selects the right sub-skill based on your input—firmware image files, extracted rootfs, physical boards, automotive ECUs, or UEFI packages. - Cross-Domain Handoff: Redirects discovered network protocols to protocol analysis and embedded malware to malware analysis skills. - Use Case: You receive an IoT router firmware update (.bin). The skill guides you to confirm ARM big-endian architecture first, unpack with binwalk, analyze the rootfs startup scripts to find entry points, then emulate the target binary in an isolated QEMU sandbox. ## Quick Start Analyze this firmware image router-fw.bin by unpacking it, examining the root filesystem, and emulating the main service binary in an isolated environment.

Frequently Asked Questions about re-firmware

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

FAQPage Schema
How do I analyze an IoT firmware image file?▼

Start with triage to identify architecture and endianness, then unpack with binwalk or unblob, analyze the extracted rootfs for startup scripts and hardcoded credentials, and emulate target binaries with QEMU. The skill routes each step to the appropriate sub-skill automatically.

What tools are used for firmware extraction and emulation?▼

Extraction uses binwalk and unblob for automatic unpacking plus manual magic-byte scanning with dd for custom vendor headers. Emulation prefers QEMU user-mode as the lightest option, with full-system emulation available when needed.

Should I use hardware access or firmware file analysis first?▼

Always analyze the firmware file first through extraction, rootfs analysis, and emulation. Hardware access via JTAG, UART, or flash reading is the last resort because it costs more, risks damaging the board, and is only needed when no firmware file is available.

Why does binwalk fail to unpack my firmware image?▼

Automatic unpacking fails when vendors use custom headers or encryption layers around standard filesystems. The fallback is manual magic-byte scanning to locate embedded filesystems, then carving them out with dd at the discovered offsets.

Can this analyze UEFI firmware and BIOS update packages?▼

Yes, UEFI targets such as BIOS updates, DXE drivers, and bootkits are routed to the dedicated UEFI sub-skill, which uses UEFITool for parsing and OVMF for emulation.

Why must firmware emulation run in a network-isolated sandbox?▼

Emulated firmware may contain code that connects back to external servers, exposing your network or alerting the device vendor. The workflow mandates sandboxing with network isolation by default, and any observed communication is handed off to protocol analysis.