Poisoned Pipeline

Poisoned Pipeline / Techniques / T0201

T0201 · Impact · TA12 · observed in 19 incident(s)

Customers compromised

Artifact Security CI/CD Posture Open Source Security

The downstream consequence of a software supply-chain attack: customers who
consumed a poisoned update, package, or service are themselves breached.
SolarWinds Orion, 3CX, Codecov, and Polyfill.io are canonical examples —
the supplier is the delivery vehicle; customer environments are the prize.
Modeling this as its own Impact technique lets defenders map "what happened
to us because we trusted a vendor" without collapsing it into a generic
backdoor label.

Where this idea came from

Original corpus

This catalogue, from upstream issue #84 (Impact: customers compromised).

Mitigations

Detections

Observed in incidents (19)

References