What this tests

parsingmonitoring

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

Anatomy

A buffer overrun in Cloudflare's HTML parser leaked uninitialized memory into served pages — session cookies, API keys, passwords, fragments of other people's HTTPS traffic, appended to responses like a free gift nobody ordered. For months it bled into cached pages that search engines dutifully indexed, meaning the leak has a permanent public archive. Named Cloudbleed, because the industry can never resist a portmanteau. The truly horrible part for clients: the response is YOUR response, correct and well-formed — plus someone else's data appended to it, silently. Not an error. A donation. Every parser that validates "is this JSON" will reject the trailing garbage; every parser that stops at the first valid document will ingest it unnoticed, which is worse. This specimen serves a valid body followed by a fragment of leaked session data. What your client does with the extra bytes — reject, ignore, or store in a database where an auditor will eventually find it — says everything about its validation discipline.

Source: Cloudflare — incident report on memory leak caused by parser bug · 2017-02-23

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[] Body:{"user":{"id":12345,"name":"ada"},"ok":true} Corrupt:leak Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-046 — Dependency self-sabotage (colors.js, Jan 2022) FD-2026-077 — Digitally signed malicious update (SolarWinds SUNBURST, 2020) FD-2026-078 — CDN domain takeover poisons the dependency (polyfill.io, 2024) FD-2026-079 — Covert payload in a trusted package (event-stream, 2018) FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-035 — Stack trace in the error body