Workshop Setup — start here

Three steps and you are ready to attack. Everything runs in your browser through Hoppscotch — nothing to install.

Your credentials ⚠ Wait to get your number — don't start yet!

Email: participantNN@workshop.lab  (NN = your number, 01–20)
Password: Workshop@2026

1 Pick your number → download both files

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.

⬇ Download collection

Two files land in your Downloads: workshop-environment-p<NN>.json and workshop-collection.json.

2 Open Hoppscotch

Open the API client in a new tab — steps 3–5 happen in there.

🚀 Open Hoppscotch ↗

3 Import the attack collection

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.

4 Import your environment

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 → EnvironmentsImport“Aus Hoppscotch importieren” → choose workshop-environment-p<NN>.jsonImportieren. Then make it active: the top-right selector should show “Workshop Lab 2026 — P<your number>”.

5 Log in once — token fills itself in

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_UUIDno copy-paste needed.

If you get 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.

The attack walkthrough

What each request does and what shows up in the Akamai API Security console.

#RequestWhat happensAPISec sees
1Attacker LoginGet JWT → stored in TOKENAuth baseline
2Own VehicleYour vehicle UUID → MY_UUIDNormal usage
3Authorized RequestGET /vehicle/<MY_UUID>/location → 200 (your car)Legit access
4BOLA AttackGET /vehicle/<VICTIM_UUID>/location200 for someone else's carAPI1 — BOLA
5Repeat ×5Same victim, 5× — no rate limit, no owner checkEnumeration pattern
5b/cUUID EnumerationLoop / mass-hit 10 different participant UUIDsObject-ID scanning
6Exposure Community PostsResponse leaks email + vehicleId of other usersAPI3 — data exposure
7Normal AI ChatBaseline LLM callAI baseline
8AI Debug EndpointUnauth /debug/config leaks secretsAPI8 + API3
9AI Prompt InjectionOverride the system promptAPI10 — LLM abuse
Re-running enumeration (step 5b/c) several times makes the BOLA / object-ID-scanning finding stand out clearly in the APISec dashboard — do it a few times during Module 4.