How you cross
-
01
Choose
Find a lab and see what you will be working with.
-
02
Start
/start <lab>on Discord. You get your own instance. -
03
Act
Use your own tools. Kali, Parrot, Linux — whatever you already run.
-
04
Submit
/submit <lab> FLAG{...}on Discord.
DESCRIPTION
It is easy to stall before you start. There is no lab, nobody to practice on, and a guide ends the moment you type its command. Here you get a situation that is already standing: someone else's assumptions, your own instance, and one trace nobody highlights. Discord starts it. The tools stay yours.
LEARNING
You learn when something will not give and you have to see why yourself. The flag confirms it. Your name stays beside the crossing. You do not need to know anything at the start. The labs run from the easiest up, so the first time can be this one.
INSTANCE
The instance stands only for you. Nobody shares that machine, and nobody watches the attempt. What you break stays on your side. When you finish, the instance goes quiet. The crossing is what remains.
TOOLS
There is no browser terminal here to lead you by the hand. You work with what you already have: Kali, Parrot, plain Linux, a notebook. The lab will go dark eventually. The terminal stays, so the skill has to live with you, not in a window that closes.
QUIET
At the start nothing tells you the next move. That quiet does not mean you are in the wrong place. The situation has no narrator. You stay with it until it shows you where to begin. A wrong move does not close it.
MARK
The work stays quiet. The record is public. After the flag a name stays on the board: who crossed, and who was first. An empty board is waiting for the first entry. First Blood is a mark left on the crossing, not a prize.