What this tests

parsingsemantics

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

TSB migrated 1.3 billion customer records to a new platform over a weekend and discovered on Monday that the migration had gone catastrophically sideways — customers logging in were shown OTHER customers' accounts. Not an error page: a perfectly rendered dashboard containing a stranger's balance, which is a data breach wearing a UI. Weeks to fix, millions in compensation, a CEO gone. The specimen models the client-visible shape: a 200, a valid response, correct schema — and somebody else's data in it. Every field parses. Nothing is technically "wrong" except the contents. There is no status code for "this is a different human". This is the hardest class in the catalogue to defend against, because the only defense is noticing — checksums, sanity bounds, "why does user 12345 have a different name than yesterday". Clients that validate structure pass. Clients that validate identity, and there are few, pass harder.

Source: UK Parliament Treasury Committee report on TSB IT failure · 2018-04-23

Replay it

curl -i https://faultydata.com/r/FD-2026-062

// response appears here

Signature

{Status:200 Headers:map[] Body:{"account":"GB29NWBK60161331926819","name":"NOT-YOUR-NAME","balance":99999.99,"note":"this is somebody else\u0027s account"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-035 — Stack trace in the error body FD-2026-095 — Sleeper payload in a trusted release (xz/liblzma, Mar 2024) FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-013 — Wrong types in a valid envelope FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)