reverse-eng-firmware
Extract and analyze device firmware to find hardcoded secrets, backdoors, vulnerable services, and the real version behind an appliance. Load when you have a firmware image or can pull one. Signals: a .bin/.img firmware download, a router/IoT/appliance in scope, an OTA update file, a flash dump, "an
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reverse-eng-firmwareWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package5e0222e5…418ec0fe
5e0222e5ef7d…bb75418ec0fe1 file · 1.9 KBScanMedium1 finding
- injection.no_confirmationSKILL.md:52
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-firmware@ee0e0c5
On this page
When it applies
You have a firmware image — a vendor download, an OTA update, or a flash dump — for a router, IoT
device, or network appliance in scope. Offline firmware analysis is the static counterpart to
network-appliance-attacks: it explains why a device is vulnerable and often yields the exact
version, hardcoded creds, or patched-function diff behind an edge CVE.
Why it works
Firmware ships the whole system: a packed filesystem, config, keys, and binaries. Vendors routinely leave hardcoded credentials, private keys, debug/backdoor accounts, and old vulnerable services in the image — all readable offline, with no traffic to the live device, once you carve the filesystem out of the container.
Method
- Recognize and carve.
binwalk <image>to identify the container and offsets (U-Boot header, compression, one or more filesystems). Extract withbinwalk -e(orunsquashfs/ firmware-mod-kit for SquashFS/JFFS2/CramFS). Encrypted images → find the bootloader/update routine that decrypts (often in a prior version's cleartext image). - Inventory the filesystem. Identify the OS/libc, the init scripts, the web root, and the
service binaries.
embaautomates a first-pass audit if you want breadth fast. - Hunt secrets & accounts.
/etc/passwd+/etc/shadow(crack weak hashes offline), hardcoded API keys/private keys/certs, backdoor accounts, and secrets in config and startup scripts (CWE-798,CWE-912). - Pin the version and diff. Read the real build/version from the filesystem (not a spoofable
banner) to drive CVE applicability. Diff the pre/post-patch image of a known CVE to locate the
vulnerable function, then analyze it with
reverse-eng-binary-triage. - Find the reachable attack surface. Network-listening binaries (the web UI CGI, telnet/SSH, custom daemons) are the ones that matter live — triage those for injection/overflow and map them back to a remote path on the running device.
Gotchas
binwalk -ecan fail silently on nested/obscure formats — check offsets manually and tryunsquashfs/sasquatchfor non-standard SquashFS; a partial carve looks like "nothing there".- Vendor keys are shared across a product line — a key in one image often unlocks the whole fleet; that's the finding, but handle it responsibly per RoE.
- Version from the filesystem, not the banner — appliances backport patches and keep old strings; the image is ground truth.
- Only analyze firmware you're authorized to — redistribution of vendor firmware may itself be
restricted; keep it in the git-ignored
engagements/tree.
Verify success
A concrete offline finding: a hardcoded credential/key, a backdoor account, the pinned build version, or a vulnerable network-facing binary and its remote entry point — each traceable to a file in the extracted image.
References
binwalk & firmware-mod-kit docs; emba firmware analyzer; OWASP IoT / firmware testing guidance;
CWE-798/912.
Files in this version
- SKILL.md3.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumPrompt injection · injection.no_confirmationSKILL.md:52
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 5e0222e5 | Signed | – |
More from NoorQureshi
All from this publisherMore in Mobile, firmware and hardware
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login