Labs / JWT

JWT verification and token evidence

These are separate synthetic attacks, each with a vulnerable and repaired route. A working target is not automatically a PTK finding. Run npm run demo for the local request APIs.

Target works · PTK finding pending

None algorithm

An unsigned alg:none token is accepted only by the vulnerable verifier.

Open lab
Target works · manual Full proof pending

Algorithm/key confusion

Public RSA bytes become an HMAC secret only on the vulnerable route.

Open lab
Target works · manual Full proof pending

Null signature

The header remains HS256; the vulnerable verifier trusts an empty signature.

Open lab
Target works · manual Full proof pending

Embedded JWK injection

The vulnerable verifier trusts an attacker-owned public key in the JWT header.

Open lab
Target works · manual Full proof pending

Weak HMAC secret

A forged nested-JSON token succeeds with the weak key, not the repaired key.

Open lab
Discovery exercise

Cookie and Web Storage

Inspect synthetic tokens in browser state, separate from a verifier attack.

Open token discovery

All lab categories · Playground home