competition-reverse-pwn

Guides reverse engineering, DFIR triage, and exploit development for CTF binary challenges.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-reverse-pwn-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-reverse-pwn
Source: https://github.com/dbx0/skills/tree/main/skills/binary-re-pwn/exploitation/competition-reverse-pwn
Command: npx skills add https://github.com/dbx0/skills --skill competition-reverse-pwn-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It provides a structured methodology for tackling binary-heavy CTF challenges—reverse engineering, malware unpacking, memory dump and PCAP inspection, crash debugging, and exploit verification—without losing evidence integrity or mixing up original and modified artifacts. ## Core Features & Use Cases - Reverse and Forensic Triage: Separates loader, payload, config, and post-decode behavior while correlating files, memory, logs, registry, and PCAPs into one execution graph. - Native Exploit Path: Maps mitigations, libc/runtime, syscall surfaces, and protocol framing, recording primitives, leaks, and target objects separately. - Evidence Discipline: Preserves offsets, hashes, crash state, and decoded artifacts as distinct files tied to observable boundaries. - Use Case: During a CTF, after the sandbox orchestrator routes a pwnable challenge here, triage the binary's mitigations, reproduce a crash from a clean baseline, and document the leak and primitive needed for the exploit chain. ## Quick Start Ask the agent to triage and reverse the provided challenge binary under the established sandbox assumptions, then verify the exploit primitive from a clean baseline. ## Quick Start Note This skill activates only after $ctf-sandbox-orchestrator has established sandbox assumptions and routed the task here.

Frequently Asked Questions about competition-reverse-pwn

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

FAQPage Schema
How do I approach a CTF reverse engineering challenge?

Start with passive triage: file type, headers, sections, imports, strings, entropy, and resources. Then decide whether the path is reverse-first, DFIR-first, or exploit-first, and tie every claim to an observable boundary like a decode edge or crash edge.

How to verify a pwn exploit primitive in a CTF?

Record the primitive, controllable bytes, leak source, and target object separately, then replay it from a clean baseline. Compare host, libc, loader, and framing differences before doubting the primitive itself.

When should this skill be used instead of other CTF skills?

Use it for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives. Specialized tasks like firmware layouts, PCAP protocol reconstruction, or container escapes route to dedicated sibling skills.

Can this skill be used without the CTF sandbox orchestrator?

No. It is a downstream specialization that requires $ctf-sandbox-orchestrator to have already established sandbox assumptions, node ownership, and evidence priorities before activation.

What evidence should be preserved during binary analysis?

Keep offsets, hashes, section names, imports, config blobs, crash registers, heap or stack shape, leak addresses, and protocol steps. Store original, decoded, dumped, and instrumented artifacts as separate files to avoid contamination.