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 new maintainer offered to help with event-stream — a package downloaded two million times a week — was given commit access, and quietly added a dependency containing an encrypted payload that activated only inside one specific build (a Bitcoin wallet's, naturally). Nobody noticed for two months because the malicious code was shipped as a real, working, useful update. It wasn't a saboteur breaking things; it was a saboteur maintaining things. The specimen serves a package tarball-ish response that is valid, useful, and contains an encrypted blob the comment swears is "test data". Structurally fine. Semantically a sleeper agent. This is the hardest class: the fault isn't a malformed artifact, it's a well-formed artifact with intentions. Parsers can't help you here — only review can, and review is the control everyone skips because "it's a popular package". Exactly.

Source: npm blog / GitHub advisory — event-stream@3.3.6 flatmap-stream incident · 2018-11-26

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Disposition:attachment; filename="flatmap-stream-0.1.1.tgz" Content-Type:application/octet-stream] Body:PK\x03\x04 — package contents — module.exports=doSomethingUseful; // test data: A75F2E9B0C4D1E3F (encrypted, definitely just test data) 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-077 — Digitally signed malicious update (SolarWinds SUNBURST, 2020) FD-2026-078 — CDN domain takeover poisons the dependency (polyfill.io, 2024) FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-035 — Stack trace in the error body