Poisoned Pipeline

Image for Poisoned Pipeline

TL;DR

🚀 What it does: Public catalogue of software supply-chain incidents mapped to techniques, platforms, and guidance frameworks

💡 Best for: Defenders, researchers, and speakers who need real supply-chain incidents mapped to technique matrices

🔍 Key features: 500+ documented incidents, 127-technique matrix, CI/CD pipeline matrix, OWASP/NIST/SLSA/CISA guidance mapping


Poisoned Pipeline (poisonedpipeline.com) is a catalogue of real-world software supply-chain incidents, maintained by Cyfinoid Research. Every incident is mapped to a technique taxonomy, the platforms it hit, and the guidance frameworks defenders already use. As of early November 2026 it documents 507 incidents across 127 techniques, spanning five decades of vendor-updater history through the 2025-2026 worm/ATO wave.

Project Overview

Supply-chain security talks and articles tend to recycle the same handful of case studies: SolarWinds, Log4Shell, xz Utils. Poisoned Pipeline started from a different observation: the actual incident record is much larger and much more varied, and most of it is scattered across vendor advisories, research posts, and CERT notes that nobody has indexed against each other.

The catalogue fixes that. Each incident entry cites its original public source, lists the techniques observed, and links to every other incident sharing those techniques. Coverage is tested against public datasets rather than only against the feeds the site reads: The Backstabber’s Knife Collection (Ohm, Plate, Sykosch and Meier, DIMVA 2020), the upstream supply-chain attack dataset maintained by tstromberg, and CERT/CC vulnerability notes all serve as checklists, with every incident entry still citing the original research.

Key Features

Technique Matrix

CI/CD Matrix

Incident Mapping

Guidance Mapping

Data and Maintenance

Quick Start

  1. Open poisonedpipeline.com for the dashboard: incidents per year, most-used techniques, and platform breakdowns
  2. Browse the technique matrix to find attack patterns by tactic
  3. Use incident mapping to pull the documented cases behind any technique
  4. Check the guidance mapping when turning findings into controls

A Cyfinoid Research catalogue mapping real supply-chain incidents to techniques, platforms, and defense guidance.