Playing as a team

CTF Team Guide: Capture the Flag Formats, CTFtime Rating and a First-Month Plan

Capture the flag competitions reward preparation as much as talent. This guide covers the formats, the categories, how CTFtime ranks teams, and how a new group can organize its first month of play.

Hexfield editorial

  1. 01

    Inspect

    Read the task, download every file, note sizes, types and hashes before touching anything.

  2. 02

    Hypothesize

    Write down what the author probably wants you to notice and how you would test it.

  3. 03

    Test

    Try the cheapest test first. Script it so it can be rerun when the idea changes.

  4. 04

    Solve

    Submit, then write the solve down while the details are fresh. The notes are the real prize.

Entropy plot of a short x86 shellcode sample, low and jagged across a few hundred bytes
Entropy of an x86 shellcode sample: short, dense code that a pwn player reads in a debugger long before any tool can classify it.

A CTF team is a group of players who enter capture the flag competitions together and share one scoreboard entry. Each challenge hides a flag, a string in a known format such as flag{...}, and submitting it earns points. Capture the flag competitions run almost every weekend somewhere in the world, most of them online, and the ones that matter for rankings are listed on CTFtime. This guide explains the formats, the usual categories, the rating, how teams divide the work, and a realistic plan for the first month.

Capture the flag formats

Jeopardy is the most common format. The organizers publish a board of tasks grouped by category, each with a point value, and teams solve them in any order. Many events use dynamic scoring, where a task’s value falls as more teams solve it. Events usually last 24 or 48 hours, and the final ranking is by points, with ties broken by the time of the last solve.

Attack-defense gives every team an identical set of vulnerable services on its own machine or network segment. Teams patch their copies while attacking the others, and a game server plants fresh flags every round, often every few minutes. Points come from stolen flags and from keeping services up. Many prestige finals use this format, and it demands a different skill set: fast patching, traffic monitoring and automated exploit runners.

King of the Hill (KotH) puts teams in a fight over shared targets: whoever controls a machine or service at check time scores. It appears less often, usually as a side event or part of a final.

Mixed formats exist as well, for example a jeopardy qualifier followed by an attack-defense final for the top teams.

Categories and the skills behind them

Pwn, or binary exploitation, asks for a remote shell or memory read through a bug in a compiled service: stack and heap overflows, format strings, use-after-free. Reverse engineering hands over a binary that checks a key or hides an algorithm. Crypto covers broken constructions, from a reused nonce to a small RSA exponent. Web covers injection, authentication flaws, deserialization and server-side request forgery. Forensics asks players to recover data from disk images, memory dumps, packet captures or damaged files. Misc collects everything else: esoteric languages, OSINT, programming puzzles, steganography.

Forensics and reversing often start with an unknown blob, which is where picture-based triage helps. The guide to binary data visualization shows how to classify a file region in a minute, and the Veles tool page covers one viewer built with CTF tasks in mind.

How CTFtime and its rating work

CTFtime.org is the shared calendar, results database and ranking site of the scene. Events are announced there with dates, format and a weight. After an event, the organizer’s scoreboard is imported, and each team’s result turns into rating points.

The 2017 formula combines four inputs: the team’s points as a share of the winner’s points, the inverse of the team’s place, the event weight, and the number of teams that scored more than zero. Only a team’s 10 best results in a calendar year count toward its yearly rating, so playing more events does not inflate it. Weights are set by admins or by team votes; new events and events under 25 have a vote limit of 25, and others can reach at most 1.5 times last year’s weight, or 2 times for attack-defense events. Since 2021 only teams that played at least two events can vote.

Joining an existing CTFtime team works through a membership request that current members approve or an invitation code. A team cannot be deleted once created, so pick the name with care.

How a CTF team forms and splits work

Most groups start from a university club, a workplace or an online community, and a new CTF team rarely needs more than three or four committed players to begin. A useful early rule: one shared channel per event, one thread or document per task, and a status line on each task saying who is on it and what has been tried. Duplicated effort is the most common waste of CTF time, and the second most common is a player stuck alone on a hard task for ten hours without asking for a second pair of eyes.

Teams usually settle on rough category owners, but flexibility matters more than titles. A reverser who finds the bug in a pwn task hands it to whoever writes exploits fastest. Before the event, someone should check the rules for team size limits, flag format and whether automated scanning is allowed. During it, one person should watch the announcement channel and the scoreboard. Afterward, short writeups turn one weekend into material the whole team can learn from; the Hexfield blog collects worked solutions in that spirit.

Tools to install before the first event

A Linux machine or VM with Python 3 and pwntools, gdb with a helper such as pwndbg or GEF, and Ghidra covers most pwn and reverse tasks. Burp Suite or a similar proxy handles web. CyberChef decodes most encodings in the browser. Wireshark reads packet captures. SageMath and the PyCryptodome library carry most crypto work, with z3 for constraint solving. binwalk and an entropy view help with firmware and forensics files.

A first-month plan for a new team

Week one: register the team on CTFtime, set up the shared channel and a notes template, and install the toolset on every member’s machine. Work through picoCTF practice problems, which Carnegie Mellon keeps online all year, so everyone solves at least a few tasks in each category.

Week two: enter one weekend jeopardy event with a low weight on CTFtime. The aim is to test the process; the final place hardly matters. Track how CTF time was spent per task and which category nobody could start.

Week three: fill the gap. If nobody touched pwn, two players spend the week on stack overflows and return-oriented programming using a wargame such as OverTheWire or pwn.college. Read two or three writeups of tasks from week two that went unsolved.

Week four: play a second event, ideally one with more categories, and write up every solved task within three days. By the end of the month the CTF team has a working routine, a first entry in the ranking and a short list of skills to build next. Capture the flag competitions reward that loop of play, review and practice far more than any single brilliant solve.

Questions readers ask

How many players does a CTF team need?

Most online jeopardy events set no limit or a generous one, and a group of three to six active players can cover the main categories. Larger teams help in 48-hour events and attack-defense finals, where someone must watch the network, patch services and run exploits at the same time. Some university and onsite events cap the roster, so read the rules first.

Do I need to register on CTFtime to play?

No. Each event has its own registration on the organizer's scoreboard. CTFtime only collects results afterward. Registering the team there is still worth it: results get linked to the team page, the yearly rating counts them, and members who joined the team before an event can vote on its weight.

Which category should a beginner start with?

Web and forensics usually have the gentlest entry, because the tools are familiar and the first challenges need little theory. Reverse engineering and pwn take longer to learn but are where many teams are short of players. Picking one category and solving every easy task in it across several events builds skill faster than sampling everything.

Are writeups allowed after a CTF ends?

Almost always, and publishing them is part of the culture. Most events ask that nothing be shared while the competition runs. After it closes, CTFtime links writeups to each task, which makes them a large free library for learning how specific challenges were solved.