Skip to content
ctfpal
Every CTF
2025weight 55.00Project Sekai

SekaiCTF 2025

74 challenges with 164 published community solutions between them. Solution links go to CTFtime’s task page, which aggregates every writeup for a challenge - individual blog posts rot, the aggregator does not. 30 of them also carry the solution SekaiCTF 2025’s own organisers published, which is linked on the challenge itself.

Full task list on CTFtime

Misc26

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

Solve it with:Brainfuck and esolang decoderCipher identifier and automatic decoderRegex tester with match offsets and capture groupsLearn: Recognising encodings

Uncategorised16

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

Solve it with:Cipher identifier and automatic decoderLearn: Recognising encodings

Reverse engineering10

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

Solve it with:Strings extractor for binaries and blobsWebAssembly disassemblerJava .class disassemblerPython .pyc bytecode disassemblerLearn: Binary exploitation

Cryptography9

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.

Solve it with:Cipher identifier and automatic decoderVigenere cipher solver with automatic key recoveryRSA decryption and attack runnerWiener’s attack on small RSA private exponentsIn-browser hash cracker with rule transformsLearn: Classical ciphers and frequency analysisLearn: RSA and the parameters that break it

Web9

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

Solve it with:JWT decoder and signature verifierJWT alg=none bypass generatorWeb attack payload catalogJWT secret brute forceLearn: Sessions, tokens and access control

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.

Solve it with:ROP gadget finderShellcode assembler and libraryCyclic pattern generator and offset finderFormat string exploit builderLearn: Binary exploitation

Other 2025 events