Skip to content
Every CTF
2025from public repositories

3108CTF 2025

27 challenges with 27 published solutions between them. CTFtime has no listing for this event at all, so nothing built on CTFtime can show what it was made of. These writeups were found in public repositories instead. Each link is pinned to the commit it was read from.

Where these writeups live

Web5

Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.

Misc5

Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.

Reverse engineering5

Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.

OSINT4

Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.

Cryptography3

Recover a plaintext or a key from something that was supposed to protect it. In practice: identify the scheme, find the parameter the author got wrong, exploit it.

Uncategorised2

The upstream scoreboard did not say, so neither do we.

Forensics2

Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.

Binary exploitation1

Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.

Other 2025 events