What this tests

parsing

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

Anatomy

The body contains {"id":1,"id":2,"id":3} — perfectly parseable, syntactically valid, and semantically a coin flip. JSON's spec says nothing about duplicates; parsers get to choose. Most take the last value. Some take the first. A few throw. None of them are wrong, which is exactly the problem — the spec delegates a security decision to implementations. This is a real attack vector, not just a parsing quirk: duplicate keys have been used to smuggle different values past validation layers that parse the same document differently — the WAF reads id:1, the app reads id:3, and suddenly you're somebody else. It's the parser-disagreement genre, the same family that makes HTTP request smuggling possible. Your client will parse this fine and get one of three ids. The question is whether it notices, or just picks a value and carries on like a man who found three doors and chose one without checking the labels.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt:dup-keys Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-011 — Truncated JSON body FD-2026-012 — Malformed JSON (trailing comma) FD-2026-013 — Wrong types in a valid envelope FD-2026-014 — Encoding mismatch (claims UTF-8, sends Latin-1) FD-2026-015 — UTF-8 BOM prefix FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024)