OPUCC 2026
29 challenges with 29 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 liveForensics6
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
Aduhai
1 official solutionAduhai2
1 official solutionAduhai3
1 official solutionMemorysoup
1 official solutionSusexe
1 official solutionTheonethatgotaway
1 official solution
Uncategorised6
The upstream scoreboard did not say, so neither do we.
Clevelandjr
1 official solutionClockwork
1 official solutionDuckvm
1 official solutionSuperbabyre
1 official solution
Web5
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Agent
1 official solutionArrayescape
1 official solutionOtpcanbebroken
1 official solutionSqlimaybe
1 official solutionUnihive2
1 official solution
Binary exploitation4
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Borrowedcode
1 official solutionGhost
1 official solutionShellcoder
1 official solution
Misc3
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Brainduck
1 official solutionShadeofduck
1 official solutionSofea
1 official solution
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.
Onelineduck
1 official solutionSharingiscaring
1 official solutionTablefortwo
1 official solution
OSINT2
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Childhoodgame
1 official solutionTaxmeifyoucan
1 official solution