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
Nation-state actors slipped SUNBURST into SolarWinds Orion build pipeline, and the malicious update shipped to ~18,000 organisations with a valid digital signature — the update mechanism worked perfectly, which is what makes it the scariest specimen in the building. Signed, checksummed, delivered, installed: every control passed, because the corruption happened before the controls ran. The specimen serves a plausibly-signed update payload — Content-Type application/octet-stream, a body that looks like a legitimate hotfix with a marker inside. Your pipeline will verify the signature, because the signature is fine, and install it, because the signature is fine. That is the entire lesson and it cost several governments a very bad year. Validation that stops at "is it authentic" is half a control. The other half — "is it sane" — is what specimen pipelines are for.
Source: CISA Alert AA20-352A — Advanced Persistent Threat compromise of government agencies · 2020-12-13
Replay it
curl -i https://faultydata.com/r/FD-2026-077
// response appears hereSignature
{Status:200 Headers:map[Content-Disposition:attachment; filename="SolarWinds-Core-v2020.2.1-Hotfix.msp" Content-Type:application/octet-stream X-Signature:sha256:valid] Body:OrionImprovementBusinessLayer.2 — SIGNED UPDATE — [sunburst-marker] — applies cleanly, unfortunately Corrupt: 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-061 — Memory leak served in responses (Cloudbleed, Feb 2017) 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