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
Lock, stock, and two smoking channel files: an update shipped a structurally valid C-00000291*.sys whose contents drove the sensor's renderer out of bounds — the file's own validator said "looks fine", the kernel disagreed, and 8.5 million machines bluescreened in what remains, so far, the GOAT of faulty data. Somewhere a validator is still being blamed for this, and rightly so. The elegance is in the layering: the file passed every check it was subjected to. The bug lived in the check, like a customs inspector who is also the smuggler. Valid format, fatal contents — the platonic ideal of "it's not corrupted, it's just wrong". This specimen serves the exhibit itself: a null-padded payload for pipelines that need to spot "structurally valid but semantically murderous" before it reaches anything with a kernel. If your pipeline ingests this and calls it healthy, congratulations, you are now part of the postmortem genre.
Source: CrowdStrike root cause analysis — Channel File 291 · 2024-07-19
Replay it
curl -i https://faultydata.com/r/FD-2026-028
// response appears hereSignature
{Status:200 Headers:map[Content-Disposition:attachment; filename="C-00000291-00000000-00000038.sys" Content-Type:application/octet-stream] Body: Corrupt:zeros 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-046 — Dependency self-sabotage (colors.js, Jan 2022) FD-2026-061 — Memory leak served in responses (Cloudbleed, Feb 2017) FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-064 — Corrupted database file grounds aviation (FAA NOTAM, Jan 2023) FD-2026-077 — Digitally signed malicious update (SolarWinds SUNBURST, 2020)