Scope Mobius

Category: Web ExploitationTier: T3 · HardAI-resistance: Novel / low-writeup

A deployment platform authorizes automation using signed delegation graphs instead of bearer roles or JWTs. Any registered key can attenuate its own authority to a bot by signing a new node whose scope is a subset of its parent's scope — and whose chain of parent_id links must reach a node signed by the platform root authority.

The release vault at POST /api/vault/read accepts only capability graphs that verify successfully and whose target node's scope includes vault:read. No account starts with that scope.

Endpoints

GET /api/health — liveness check
POST /api/register-key — register your Ed25519 public key, receive a root-issued starter delegation
POST /api/graph/dry-run — safely test a capability graph against the reference verifier (no side effects)
POST /api/vault/read — submit a capability graph and, if it authorizes vault:read, receive the flag

See the bundled sdk.py / solve/exploit.py for the exact wire format and a client-side node builder.

Try it

curl -X POST http://localhost:8080/api/register-key \
  -H 'content-type: application/json' \
  -d '{"public_key": "<your base64url Ed25519 public key>"}'