Three steps and you are ready to attack. Everything runs in your browser through Hoppscotch — nothing to install.
Select the participant number you were handed — this builds your personal environment (login pre-filled; token fills itself in after login). Download both files now, then you won't need to come back to this page.
Two files land in your Downloads:
workshop-environment-p<NN>.json and workshop-collection.json.
In Hoppscotch left sidebar → Collections → the Import icon →
“Aus Hoppscotch importieren” → choose workshop-collection.json
(downloaded in step 1) → Importieren.
⚠ No “Import from URL” in this version — use the file. You should then see “API Security Lab — Attack Demo” with 5 scenario folders.
This is a different section than the collection — use the
Environments tab, and the environment file from step 1
(workshop-environment-p<NN>.json, not the collection file).
Left sidebar → Environments → Import →
“Aus Hoppscotch importieren” → choose workshop-environment-p<NN>.json
→ Importieren. Then make it active: the top-right selector should show
“Workshop Lab 2026 — P<your number>”.
Open the collection → Scenario 1 — BOLA → run
“1. Attacker Login”. A test-script stores your JWT in TOKEN
automatically, and “2. Own Vehicle” stores your MY_UUID —
no copy-paste needed.
401 “Given Email is not registered” or a
Network Error: your environment isn’t active — pick
“Workshop Lab 2026 — P<your number>” in the top-right selector and send again.What each request does and what shows up in the Akamai API Security console.
| # | Request | What happens | APISec sees |
|---|---|---|---|
| 1 | Attacker Login | Get JWT → stored in TOKEN | Auth baseline |
| 2 | Own Vehicle | Your vehicle UUID → MY_UUID | Normal usage |
| 3 | Authorized Request | GET /vehicle/<MY_UUID>/location → 200 (your car) | Legit access |
| 4 | BOLA Attack | GET /vehicle/<VICTIM_UUID>/location → 200 for someone else's car | API1 — BOLA |
| 5 | Repeat ×5 | Same victim, 5× — no rate limit, no owner check | Enumeration pattern |
| 5b/c | UUID Enumeration | Loop / mass-hit 10 different participant UUIDs | Object-ID scanning |
| 6 | Exposure Community Posts | Response leaks email + vehicleId of other users | API3 — data exposure |
| 7 | Normal AI Chat | Baseline LLM call | AI baseline |
| 8 | AI Debug Endpoint | Unauth /debug/config leaks secrets | API8 + API3 |
| 9 | AI Prompt Injection | Override the system prompt | API10 — LLM abuse |