Featured

reverse-engineering-firmware-analysis

Name: reverse-engineering-firmware-analysis
Author: DNYoussef

Firmware extraction and IoT security analysis (RE Level 5) for routers

TL;DR

Extracts and analyzes IoT router firmware for security flaws and vulnerabilities.

What Is It

Extracts filesystems from router firmware using binwalk
Analyzes services, daemons, and network listeners
Identifies hardcoded credentials and CVEs
Performs binary analysis on extracted components

Key Features

Uses binwalk for firmware extraction
Supports SquashFS, JFFS2, CramFS filesystems
Maps init scripts and network services
Identifies injection points and hardcoded credentials
Requires isolated environments for execution
Integrates with MCP servers for security scanning
Enforces strict network isolation during analysis
MUST run in VM, Docker, or sandbox only

How to Use

1.Run /re:firmware <firmware.bin> to start analysis
2.Use --extract-only to extract filesystem only
3.Use --analyze-services to map services and daemons
4.Use --analyze-binary to inspect specific binaries
5.Always validate in isolated environments
6.Never execute firmware on host system

Guardrails & Gotchas

NEVER execute firmware binaries or extracted files on your host system!
All analysis MUST be performed in isolated VM, Docker, or sandbox
Use QEMU with -snapshot flag for emulation
Never connect emulated devices to production networks
Treat all IoT firmware as potentially compromised
Use read-only mounts for extracted filesystems

GitHub Stats

Author

@DNYoussef

Repository

DNYoussef/context-cascade

Stars

Explore More Skills

api-design-principles

@wshobson

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

21k

2.3k

3mo ago

reverse-engineering-firmware-analysis

Explore More Skills

api-design-principles

prd

revenuecat