zardus/ctf-tools

★ 9,392ShellAudience · developerComplexity · 2/5Setup · moderate

Mindmap

mindmap
  root((ctf-tools))
    What it does
      Automated tool install
      CTF competition setup
      Repeatable environments
    Categories
      Binary exploitation
      Reverse engineering
      Forensics
    Key tools
      Ghidra and IDA
      GDB with pwndbg
      angr and pwntools
      QEMU emulation
    Audience
      Security researchers
      CTF competitors
    Notes
      Scripts only no tools
      Build status badges

mindmap root((ctf-tools)) What it does Automated tool install CTF competition setup Repeatable environments Categories Binary exploitation Reverse engineering Forensics Key tools Ghidra and IDA GDB with pwndbg angr and pwntools QEMU emulation Audience Security researchers CTF competitors Notes Scripts only no tools Build status badges

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Set up a complete CTF competition toolkit on a new machine without manually hunting down and installing each tool.

USE CASE 2

Install specific reverse engineering tools like Ghidra, GDB with pwndbg, or angr for binary analysis.

USE CASE 3

Automate consistent security tool environment setup across multiple analysis machines or virtual machines.

Tech stack

Shell

Getting it running

Difficulty · moderate Time to first run · 30min

Some tools require a manual download step before the installer runs (e.g., IDA), build status badges indicate which installers are currently working.

In plain English

ctf-tools is a collection of automated setup scripts for installing security research and competition tools onto a new machine. CTF stands for Capture the Flag, which is a type of hacking competition where participants solve security challenges to find hidden values. The repository does not contain the tools themselves, only shell scripts that download and install them, making it straightforward to get a full toolkit running on a fresh system without hunting down each tool individually. The tools are organized into categories. The binary category covers programs for analyzing and working with compiled executables: debuggers, decompilers, disassemblers, fuzzers, and tools for finding exploitable code patterns. Named tools include Ghidra and IDA for reverse engineering, GDB with enhanced frontends like pwndbg and GEF, angr for binary analysis, pwntools for writing exploits, and QEMU for running code compiled for different processor architectures. The forensics category includes tools for examining firmware, PDF files, and memory dumps. Each tool in the README lists a last-build status badge that shows when it was most recently verified to install correctly, which gives some indication of whether a given installer is currently working. Some tools are noted as failing or slow, and IDA is flagged as requiring a manual download step before the installer can run. The repository is intended for security researchers and CTF competitors who regularly set up new analysis environments and want a repeatable way to install a standard suite of tools without spending time on configuration. It assumes familiarity with the tools themselves and does not include guides on how to use them.

Copy-paste prompts

Prompt 1

I'm setting up a new CTF competition environment from scratch. Walk me through using ctf-tools to install Ghidra, pwndbg, and pwntools, and verify they're working.

Prompt 2

Show me how to use pwntools (installed via ctf-tools) to write a basic buffer overflow exploit for a simple vulnerable binary.

Prompt 3

I need to analyze a firmware image for a CTF forensics challenge. Which ctf-tools installers should I run, and how do I use the installed tools to extract the filesystem?

Prompt 4

How do I add a new tool installer to the ctf-tools repository, what's the expected directory structure and script format?

Prompt 5

Use angr (from ctf-tools) to automatically find the correct input that reaches a specific function in a CTF binary, show me a minimal Python script.

Open on GitHub → Explain another repo

← zardus on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.