ctf-reverse
ctf-reverse equips you with techniques for analyzing compiled, obfuscated, packed, and virtualized targets in CTF competitions. It covers static analysis tools like GDB and Ghidra, dynamic approaches with Frida and angr, emulation frameworks, anti-analysis bypass strategies, and language-specific reversing for Python bytecode, WASM, Android, and compiled languages. Use this when understanding the target's behavior is the blocker before exploitation.
ctf-reverse helps you understand compiled, obfuscated, or packed binaries before exploitation in CTF challenges.
AI-generated summary based on this skill's SKILL.md
Install
ljagiello/ctf-skills/ctf-reverse · repository language: Python
git clone https://github.com/ljagiello/ctf-skills
cp -r ctf-skills/ctf-reverse ~/.claude/skills/ctf-reversenpx skillfed install ljagiello/ctf-skills/ctf-reverseFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is ctf-reverse and when should I use it?
ctf-reverse equips you with techniques for analyzing compiled, obfuscated, packed, and virtualized targets in CTF competitions. Use it when understanding the target's behavior is the blocker before exploitation. It covers static analysis tools like GDB and Ghidra, dynamic approaches with Frida and angr, emulation frameworks, anti-analysis bypass strategies, and language-specific reversing for Python bytecode, WASM, Android, and compiled languages.
How do binary reversing techniques help in CTF challenges?
ctf-reverse teaches binary reversing techniques that let you understand compiled binaries before attempting exploitation. By combining static analysis (disassembly, decompilation) with dynamic analysis (debugging, instrumentation), you can map program logic, identify vulnerabilities, extract flags, and understand protections. These techniques apply across x86, ARM, WASM, and other architectures you'll encounter in CTF competitions.
What tools does ctf-reverse cover for analyzing compiled binaries?
ctf-reverse covers major static and dynamic analysis tools: GDB for debugging, Ghidra for decompilation and binary analysis, radare2 for disassembly, Frida for dynamic instrumentation, and angr for symbolic execution. These tools work together—use static analysis to understand structure, dynamic analysis to observe runtime behavior, and symbolic execution to explore execution paths and extract flags from complex binaries.
How can I reverse engineer non-x86 targets like ARM, WASM, and APK?
ctf-reverse includes language-specific reversing techniques for non-x86 architectures. For ARM, use GDB and Ghidra with ARM-specific disassembly. For WASM bytecode, analyze the binary format and use specialized tools. For Android APK files, decompile DEX bytecode, analyze Java/Kotlin sources, and inspect native libraries. Each target type requires adapted tooling but follows the same core analysis workflow.
What anti-debug and anti-analysis protections does ctf-reverse address?
ctf-reverse covers anti-debug and anti-analysis bypass techniques to help you overcome common protections. These include ptrace detection, debugger checks, integrity verification, and obfuscation. You'll learn to identify these protections, patch them out, use alternative debugging methods, and apply dynamic analysis tools like Frida that can circumvent some defenses while maintaining stealth during analysis.
How do I extract flags using dynamic and static analysis with ctf-reverse?
ctf-reverse teaches flag extraction through combined approaches: static analysis reveals the flag-checking logic and constraints; dynamic analysis with GDB or Frida lets you observe flag validation at runtime; symbolic execution with angr can solve constraints automatically. Memory dumping and analysis help capture flags from process memory. Together, these techniques let you extract flags from packed, virtualized, or obfuscated binaries.
SKILL.md
rendered from the published skill — quoted content, verbatim
CTF Reverse Engineering
Quick reference for RE challenges. For detailed techniques, see supporting files.
Prerequisites
Python packages (all platforms): ```bash pip install frida-tools angr qiling uncompyle6 capstone lief z3-solver
For Python 3.9+ bytecode: build pycdc from source
git clone
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 15 files
ctf-reverse/SKILL.md
ctf-reverse/anti-analysis-ctf.md
ctf-reverse/anti-analysis.md
ctf-reverse/field-notes.md
ctf-reverse/languages-compiled.md
ctf-reverse/languages-platforms.md
ctf-reverse/languages.md
ctf-reverse/patterns-ctf-2.md
ctf-reverse/patterns-ctf-3.md
ctf-reverse/patterns-ctf.md
ctf-reverse/patterns-runtime.md
ctf-reverse/patterns.md
ctf-reverse/platforms-hardware.md
ctf-reverse/platforms.md
ctf-reverse/tools-advanced-2.md