Poisoned packages: the software supply chain
Supply-chain attacks · facts checked 2026-10-03
The facts
- MITRE ATT&CK lists compromising software dependencies and development tools as a supply chain technique. (MITRE)
- In March 2024 a backdoor was found in versions 5.6.0 and 5.6.1 of the XZ Utils compression library. (CISA)
- The XZ Utils backdoor was assigned CVE-2024-3094. (CISA)
- The OpenSSF Malicious Packages project collects reports of malicious packages in open source package registries. (OpenSSF)
The panel
Jordan Pike AI host
MITRE says its ATT&CK framework lists compromising software dependencies and development tools as a supply chain technique.
Jordan Pike AI host
CISA says that in March 2024 a backdoor was found in versions 5.6.0 and 5.6.1 of the XZ Utils compression library, and CISA says the backdoor was assigned CVE-2024-3094.
Jordan Pike AI host
The OpenSSF says its Malicious Packages project collects reports of malicious packages in open source package registries.
Jordan Pike AI host
So who should care? Anyone who builds software or runs it, which is roughly everyone. Maya, how does this technique work in practice?
Maya Okafor AI analyst
You don't attack the target, you attack what the target trusts. A dependency gets pulled in automatically, so a bad version arrives looking like a routine update. The facts here don't name a bug class, so I'll say it hasn't been disclosed. The weakness is trust in code nobody on your team wrote or read. A build pipeline that fetches whatever is newest is basically a very fast, very polite way to accept packages from strangers.
Rina Takahashi AI analyst
From the attacker's side, it's efficiency. One poisoned library or development tool can reach every organisation downstream, and each of them did the installing for you. A mail gateway is a classic pivot point, and a shared dependency is the same idea at scale. Nobody is attributed in these facts, and I'm not going to invent a culprit. A claim without a source is just a rumour with good branding.
Jordan Pike AI host
So: Monday morning?
Maya Okafor AI analyst
Inventory first. You can't check for the affected versions of a library if you don't know where it lives. That includes the things buried inside other things, like base images and vendor appliances. Ask your suppliers too. And remember that a clean scan today says little if you don't know how long your logs go back. Whether a backdoor was used before anyone noticed is a question for the logs.
Rina Takahashi AI analyst
Then add outside intelligence. Public collections of malicious package reports, like the OpenSSF project, can feed your build checks, so a known-bad package gets stopped before it gets installed. My mild disagreement with Maya: I'd rather new versions of dependencies wait briefly before they go into production, so other people's alarms go off first.
Maya Okafor AI analyst
A hold-back delay is fine, but it's a bridge, not a fix, so give it an end date. Pinned versions that nobody revisits turn into the old, unpatched code you'll be reading about next year. Delay, then update, with a named owner for each dependency.
Jordan Pike AI host
And for your board, put it in business terms: which products depend on which components, which customers sit on those products, and which regulator's clock starts if one turns out to be poisoned. Know what you run, delay new versions on purpose, and write down when the delay ends.





