In 2014 I stood at DEF CON and showed the internet’s foundational software was held together by wishful thinking, volunteer labor, and collective myth. Last week Anthropic’s unreleased frontier model validated that at industrial scale. This month two nation-state actors proved the security tooling itself is now the attack surface. And Project Glasswing — the response — may be the most consequential single policy decision to date in the history of open source software security. Whether that consequence is good or catastrophic depends entirely on decisions no one has made yet.
Episode guide
Three narrative threads across Season 3
Thread 1 — The vulnerability story (Ep. 01, 02, 06)
The quantitative case that OSS infrastructure was never as secure as the collective myth suggested — from Exim’s 13,000 criticals in 2014 to TensorFlow’s 700+ in 2026. The data through two generations of infrastructure.
- Ep. 01 — Internet infrastructure: DEF CON 22 dataset
- Ep. 02 — Supply chain: transitive dependency risk
- Ep. 06 — ML stack: the new load-bearing walls
Thread 2 — The attack story (Ep. 03, 04, 05)
How nation-state actors operationalized the threat models security researchers had been publishing for years. XZ as the template, Trivy as the pivot, Axios as the broadside. The playbook was published. They read it.
- Ep. 03 — XZ Utils: the two-year playbook
- Ep. 04 — Trivy/TeamPCP: the cascade
- Ep. 05 — Axios/UNC1069: the locksmith operation
Thread 3 — The response story (Ep. 07, 08, 09)
Glasswing as policy precedent. The compliance cliff. Whether the voluntary restraint that produced Glasswing is more durable than the restraint that left the bugs unfixed for 27 years. The substrate change at the governance layer.
- Ep. 07 — Glasswing: the doctrine
- Ep. 08 — The compliance cliff
- Ep. 09 — The pattern: season finale
Recurring themes across Season 3
Everybody / Somebody / Nobody / Anybody
Introduced at DEF CON 22 to explain Heartbleed. Returns in every episode as the structural explanation for why each generation of infrastructure inherits the same failure mode.
Diligence as the attack surface
The most security-conscious organizations had the greatest Trivy exposure because they ran it most frequently. The XZ maintainer was trustworthy, which is why the attack worked. Security posture as vulnerability vector.
Fairy dust moves up the stack
2014: “everyone’s looking at the code.” 2024: “our tooling is trustworthy.” 2026: “our AI deployment is safe.” The pattern is consistent. Only the substrate changes.
Nation-state math on open source
Two weeks to own 100M weekly downloads. Two years to own a transitive dependency of sshd. The economics of targeting volunteer maintainers only improve as package footprints grow.
Good intentions vs. durable structures
Glasswing is voluntary restraint. The OSS social contract was voluntary contribution. Both depend on goodwill at a scale it was never designed for. Season 3 asks what durable looks like.
Machine discovery, human remediation
Mythos finds bugs at machine speed. Patches ship at human speed. Season 3 maps what changes when discovery becomes free and the bottleneck shifts entirely to everything that comes after.
“Project Butterfly of Damocles: named for the moment you realize the sword has been hanging above the internet since 1998 — and that the thread was always a volunteer with a day job.”
— Series concept note, April 2026Episodes 01 and 07 are published as part of the series premiere. Episodes 02–06 and 08–10 are in production and will publish on a rolling schedule through Q2–Q3 2026. Subscribe to the Morphogenetic SOC newsletter at securesql.info for release notifications.
The author is affiliated with Project Glasswing. This post reflects the author’s independent analysis and opinions only, and does not represent the views or positions of Anthropic, Project Glasswing, or any Glasswing launch partner. Readers should weigh the author’s affiliation accordingly when evaluating assessments of the initiative’s merits and limitations.