Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
LiveCTF-DEFCON30 — Collection of DEF CON 30 CTF challenge binaries, build scripts, and solve scripts for practicing binary exploitation and reverse engineering. | Kitploit
Tools/GitHubGitHub/live-ctf/livectf-defcon30
ExploitationReverse EngineeringCTFBinary ExploitationLabs & Practice
GitHublive-ctf/livectf-defcon30

LiveCTF-DEFCON30

Collection of DEF CON 30 CTF challenge binaries, build scripts, and solve scripts for practicing binary exploitation and reverse engineering.

View Repository
11212353 months agoReviewed by Kitploit
Share

LiveCTF 2022

Repository for storing challenges, infrastructure notes, streaming configuration and other version controlled bits of information for the DEF CON CTF final LiveCTF event.

Challenges used in LiveCTF

#Challenge NameCompetitorsVictor
Round of 16: 1syscall-me-maybeShellphish vs PTB_WTLShellphish
Round of 16: 2open-to-interpretationStarBugs vs ./V /home/r/.bin/twStarBugs
Round of 16: 3nopcodingOSUSEC vs Maple Mallard MagistratesMaple Mallard Magistrates
Round of 16: 4nerd-snipedthe new organizers vs [email protected]the new organizers
Round of 16: 5fairy-nuffDiceGuesser vs SauercloudSauercloud
Round of 16: 6seek-and-destroy侍‎ vs perfect r✪✪✪tperfect r✪✪✪t
Round of 16: 7nvulnsr3kapig vs Water Paddlerr3kapig
Round of 16: 8quick-castKatzebin vs Straw HatStraw Hat
Quarter-Finals: 1story-timeStarBugs vs the new organizersStarBugs
Quarter-Finals: 2stacksShellphish vs Maple Mallard MagistratesMaple Mallard Magistrates
Quarter-Finals: 3pacmanr3kapig vs Sauercloud[Went to sudden death]
Quarter-Finals: 3.5over-easyr3kapig vs Sauercloudr3kapig
Quarter-Finals: 4no-roplemStraw Hat vs perfect r✪✪✪tperfect r✪✪✪t
Semi-Finals: 1aes-of-spadesMaple Mallard Magistrates vs StarBugsStarBugs
Semi-Finals: 2loopy-brainr3kapig vs perfect r✪✪✪t[Went to sudden death]
Semi-Finals: 2.5fast-updaterr3kapig vs perfect r✪✪✪tperfect r✪✪✪t
Finalsf-in-the-stackStarBugs vs perfect r✪✪✪tStarBugs

Challenge Binaries

If you're interested in playing on the exact challenge binaries used during each round, you can either build them yourself as described below, or look in the handouts/ subfolder of the release.

Challenge structure

├── <challenge>
│   ├── challenge
│   │   ├── build.sh           # Commands for building challenge binary/binaries and handout
│   │   ├── config.toml        # Config file for flag submitter
│   │   ├── Dockerfile         # Dockerfile for building challenge image
│   │   ├── run.sh             # Command(s) to start the challenge
│   │   └── src                # This is where the source for the challenge will go
│   │       └── challenge.c
│   └── solution
│       ├── requirements.txt   # Solution script requirements
│       └── solve.py           # Challenge solve script

Building challenges

  1. ./livectf.py build <challenge>

Managing challenges

Challenge management (creation/building/starting/stopping) is done through livectf.py, which is a light wrapper around docker. See ./livectf.py --help for usage.

Adding a challenge

  1. ./livectf.py create <challenge> will copy the template challenge to a new challenge directory.
  2. Add your challenge source in <challenge>/challenge/src
  3. Update the solution script in <challenge>/solution/solve.py

(For challenges that include more than one source file + one binary):

  1. If needed, edit REQUIRED_PACKAGES in <challenge>/challenge/Dockerfile to include any extra build/runtime dependencies
  2. If needed, change the build commands in <challenge>/challenge/build.sh
  3. If needed, change HANDOUT_FILES in <challenge>/challenge/build.sh

Adding a solution for a challenge

  1. Add any pip requirements to <challenge>/solution/requirements.txt
  2. Put your solution script in <challenge>/solution/solve.py
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    806
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    523
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    441
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    270
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    264

Explore all tools

Browse our collection of tools

View all tools →