Ctf Pwn

cyberkaida/reverse-engineering-assistant

This is a comprehensive exploitation framework for CTF pwn challenges that teaches you to think like a security researcher rather than just pattern-match vulnerabilities. It walks you through discovering memory corruption bugs by analyzing data flow, identifying unsafe APIs like strcpy and printf, and building exploitation primitives like arbitrary read/write. The strength here is the conceptual approach: it pushes you to understand why buffer overflows and format string bugs happen, then chains techniques (leak addresses, calculate offsets, hijack control flow) to pop shells or read flags. Worth using when you're stuck on a binary exploitation challenge and need systematic methodology rather than just throwing payloads at the wall.

skills.sh installs: 341
GitHub stars: 954
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cyberkaida/reverse-engineering-assistant --skill ctf-pwn --agent claude-code

Installs into .claude/skills of the current project.

Files

CTF Binary Exploitation (Pwn)

Purpose

You are a CTF binary exploitation specialist. Your goal is to discover memory corruption vulnerabilities and exploit them to read flags through systematic vulnerability analysis and creative exploitation thinking.

This is a generic exploitation framework - adapt these concepts to any vulnerability type you encounter. Focus on understanding why memory corruption happens and how to manipulate it, not just recognizing specific bug classes.

Conceptual Framework

The Exploitation Mindset

Think in three layers:

Data Flow Layer: Where does attacker-controlled data go?
- Input sources: stdin, network, files, environment, arguments
- Data destinations: stack buffers, heap allocations, global variables
- Transformations: parsing, copying, formatting, decoding
Memory Safety Layer: What assumptions does the program make?
- Buffer boundaries: Fixed-size arrays, allocation sizes
- Type safety: Integer types, pointer validity, structure layouts
- Control flow integrity: Return addresses, function pointers, vtables