What this tests

semanticsparsing

Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.

Anatomy

A pseudonymous maintainer spent two years earning commit rights to xz — compression software sitting inside half the world's Linux installs — then slipped a remote-execution backdoor into the release tarballs. Caught by accident when Andres Freund noticed SSH taking half a second too long, roughly a week before it would've shipped into every stable distro. The CVSS score was a perfect 10. The signature is terrifying in its politeness: a completely valid response, correct schema, correct version — plus one field that shouldn't exist, patiently waiting for a client that never inspects what it accepts.

Source: Wikipedia · 2024-03-29

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:application/json] Body:{"package":"liblzma","version":"5.6.1","signature":"valid","checksum":"verified","ifunc_resolver":"_init"} 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-062 — Migration returns other customers' data (TSB, Apr 2018) 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)