reverse-engineering

Reverse-engineer closed-source binaries and firmware via static and dynamic analysis.

Updated Jul 1, 2026

Search Tags:#static analysis #reverse engineering #binary analysis #firmware analysis #dynamic analysis

Ready to run

npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill reverse-engineering-bpnrockstar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-engineering
Source: https://github.com/bpnrockstar/UnifiedBugHunter/tree/main/skills/reverse-engineering
Command: npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill reverse-engineering-bpnrockstar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires radare2, Ghidra, IDA Pro, GDB, Lighthouse, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill empowers users to reverse-engineer closed-source binaries and firmware, enabling them to understand what a binary does without source code, find backdoors, extract algorithms, or patch binaries.

Core Features & Use Cases

Static Analysis: Offers workflows using radare2, Ghidra, and IDA Pro for code analysis.
Dynamic Analysis: Provides guidance on GDB and Lighthouse for dynamic analysis.
Decompilation: Assists in extracting algorithms from binaries.
Protocol Reverse Engineering: Guides through protocol analysis and deobfuscation.
Binary Diffing: Offers techniques for comparing binary versions.
Firmware Analysis: Includes methods for firmware extraction and analysis.
Use Case: A cybersecurity professional needs to reverse-engineer a suspicious binary to understand its functionality and potential vulnerabilities.

Quick Start

Use the reverse-engineering skill to perform static analysis on the binary 'malware.bin' using radare2.

Frequently Asked Questions about reverse-engineering

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

FAQPage Schema

How do I reverse-engineer closed-source binaries and firmware without source code?▼

Static and dynamic analysis are used to reverse-engineer closed-source binaries and firmware without source code. Static analysis examines code structure using radare2 or Ghidra, while dynamic analysis observes runtime behavior using GDB.

What is the best way to analyze suspicious binaries for potential vulnerabilities?▼

To analyze suspicious binaries for vulnerabilities, combine decompilation with dynamic analysis. This approach reveals what the binary does and helps locate backdoors by observing its runtime behavior and extracted algorithms.

Do I need radare2 and IDA Pro to perform static analysis on malware?▼

Yes, performing static analysis on malware requires tools like radare2, Ghidra, or IDA Pro. These dependencies are necessary to dissect code structure and understand binary functionality without executing the program.

Can I extract algorithms and deobfuscate protocols from closed-source firmware?▼

Yes, you can extract algorithms and deobfuscate protocols from closed-source firmware. The process applies firmware analysis and protocol reverse engineering techniques to decipher communication patterns and hidden logic.

How do I compare different versions of a binary to find patched vulnerabilities?▼

To compare different binary versions and find patched vulnerabilities, you use binary diffing techniques. This method highlights code changes between versions, helping you identify exactly what security patches were applied.