Capture the Flag · energy and finance · Moldova · Romania · Ukraine
Getting started
- Register with the code you were given (on your handout in the room, or in your invitation email if you're online), or log in if you already have an account. Game control puts you on a team from your country; you don't need to pick one.
- Open Challenges and start with Welcome Brief.
- Five challenges run in your team's private lab. Click Lab in the top menu to open it; your scoreboard login gets you in.
Schedule (Moldova time, EET)
| Day 1, 11:15 | Onboarding and Set 1: First contact |
| Day 1, 13:45 | Set 2: Energy and Finance tracks |
| Day 2, 09:00 | Set 3: Connecting the dots |
| Day 2, 10:50 | Final round: Trident |
| Day 2, 13:30 | Scoring, solution walkthrough and lessons learned |
Rules
- Attack only the targets a challenge gives you, inside your own team's lab. The CTF site and the lab login page are off limits: breaking them breaks the game for everyone.
- Flags look like
RT{...}and are not case-sensitive. - Hints cost points. If fewer than 3 teams have solved a challenge by its set's free-hint times, its next hint becomes free for everyone: Set 1 at 12:00 and 12:30, Set 2 at 14:30 and 15:15, Set 3 at 09:35 and 10:10. Questions to a proctor about the platform are free.
- Solve a challenge before any of its hints goes free, without using a hint, and your team earns a +15% Unassisted bonus.
- Most analysis challenges lose value as more teams solve them, down to half once about half the teams have solved them; every team that solved one gets its current value. The lab challenges and the final round keep their full value.
- Overnight between the two days, from 16:30 on Day 1 to 09:00 on Day 2, the challenges, their files and your lab close and flag submissions pause. Everything reopens at 09:00. Submissions close for good at 12:30 on Day 2.
- Share freely inside your team, but never share flags between teams. In the final round you'll need to share information with other teams, and that's allowed.
- Some files are in Romanian, Ukrainian or Russian, as real evidence would be. You never need to read a language to solve a challenge, but it helps.
- Treat every file as hostile. Most malware challenges need only static analysis; a few need you to run the sample. Do all analysis, and anything you run, inside an isolated virtual machine, never on your own laptop. Samples are defanged (no encryption, data theft or spreading) but still behave like malware, so antivirus and EDR will flag them. That's why they come in zips with the password
infected.