One Request Away

One change turns this request into an exploit.

Code reviews, but for HTTP requests. Each day you get one real request that is a single change away from an exploit. Spot the value the server shouldn't trust, change it, and send it.

Free, no account Two minutes A new one daily
Today Only the first one was checked No. 27
GET /api/streams?channels=org.204.alerts&since=0 HTTP/1.1
Cookie: rw_session=8f2c9ae1b4d0
Open the drill

How a drill works

Two minutes, and the whole thing happens in the browser.

GET /api/reports/8841 HTTP/1.1
Cookie: session=s%3A61c0; tenant=AC-2
1 The request

A legitimate request, exactly as the client sent it. Somewhere in it is one part the server shouldn't trust. Nothing is marked; click the part you suspect.

Substitute Remove Add Method
2 The move

Pick what to do with it: substitute it, remove it, add to it, or switch the method. Every drill is solved with one of these four moves, one change per send.

HTTP/1.1 200 OK
{ "tenant": "AC-9", "balance": 18420.00 }
3 The response

Send it and read what comes back: a status, a body, and a short note on why. The right change triggers the issue. A wrong one gets an honest answer too, and that is usually the lesson.

Every drill

Newest first. Each one names the request it is about, so you can pick by what you want to practise.

Only the first one was checked
GET /api/streams?channels=org.204.alerts&since=0  ·  10 Nov
Unsigned means sandbox
POST /webhooks/paylink  ·  3 Nov
The deadline in your own time
POST /api/attempts/8813/submit  ·  27 Oct  ·  solved by 2
One character longer
GET /internal/billing/ledger  ·  20 Oct  ·  solved by 2
Approved on arrival
POST /api/claims  ·  13 Oct  ·  solved by 2
The cursor carries the scope
GET /api/conversations/threads?cursor=eyJvIjoyMDR9&limit=25  ·  6 Oct  ·  solved by 3
The verb in the body
POST /catalogue/releases/glasshouse-ep/collaborators  ·  29 Sep  ·  solved by 2
The link that works without it
GET /preferences?u=9330&h=6f2ab19c  ·  22 Sep  ·  solved by 2
Points that arrive before they leave
POST /api/points/transfer  ·  15 Sep  ·  solved by 2
The child you are not the parent of
GET /api/report-cards/current  ·  8 Sep  ·  solved by 5
A capital letter
GET /portal/underwriting/quotes?status=flagged  ·  1 Sep  ·  solved by 3
The file that outlived its ticket
GET /tickets/88214/attachments/307  ·  25 Aug  ·  solved by 5
Someone else’s table
POST /api/rounds  ·  18 Aug  ·  solved by 4
A filter is not a permission
GET /api/applications?owner=me&stage=screening&limit=25  ·  11 Aug  ·  solved by 3
Your token, their account
POST /account/password/reset  ·  6 Aug  ·  solved by 4
The toggle you never touched
POST /api/threads/2214/comments  ·  5 Aug  ·  solved by 3
The rule that only watched one verb
POST /api/purchase-orders/PO-3391/approve  ·  4 Aug  ·  solved by 1
A template that is not a template
POST /api/exports  ·  3 Aug  ·  solved by 3
The page after consent
GET /oauth/consent?client_id=cwl_31&return_to=/reports  ·  2 Aug  ·  solved by 3
The setting you were not allowed to change
PUT /api/workspaces/ferrymead/security  ·  1 Aug  ·  solved by 2
What the redaction missed
GET /api/candidates/8841/scorecard?format=pdf  ·  31 Jul  ·  solved by 3
A URL that changes its mind
POST /api/status-pages/9/import  ·  30 Jul  ·  solved by 4
A better price at checkout
POST /api/checkout  ·  29 Jul  ·  solved by 3
The office you are not in
POST /api/admin/session  ·  28 Jul  ·  solved by 4
An invitation with something extra
POST /api/workspaces/ellis-vane/invitations  ·  27 Jul  ·  solved by 7
The code you were not sent
POST /api/registration/verify  ·  26 Jul  ·  solved by 8
Somebody else’s invoice
GET /api/invoices/INV-4471  ·  25 Jul  ·  solved by 10
Why I made this
Marius Horatau
Marius Horatau
Creator of Uphack

Most real findings start as recognition — I have seen a request shaped like this before.

That instinct is trainable, and it comes from reading a lot of requests, not from memorising payloads. It is also the part that matters: a checklist covers the bugs everyone already knows about. On an application nobody has tested before, your read on a request is all you have.

Drills are that reading practice with the feedback attached: many small cases, each with a straight answer about what you missed. One request a day is enough. After a month of them, unfamiliar requests start to look familiar.

Thanks,
Marius Horatau’s signature
Do not stop here

A drill is one request.
A lab is the whole app.

Uphack labs are believable products with one realistic flaw buried in an ordinary feature. Same instinct, nothing highlighted — you get a running application and have to find it yourself.

Browse the labs

Drills stay free. If you want the labs the reasoning came from, registration is open until 19 September.

Create your account