Attack Library
Software Supply Chain Attacks by Year
Updated 1 Nov 2026
Our library holds 124 real software supply chain attacks from 2009 to 2026. 30 of them happened in 2026, more than in any earlier year. 5 went after the AI coding tools that staff now use to build apps.
Attacks by year
2026 has the most attacks in the library, 30. 2025 has 20. 63 of the 124 attacks happened in the last three years.
| Year | Attacks | On AI coding tools |
|---|---|---|
| 2026 | 30 | 5 |
| 2025 | 20 | |
| 2024 | 13 | |
| 2023 | 4 | |
| 2022 | 4 | |
| 2021 | 6 | |
| 2020 | 8 | |
| 2019 | 5 | |
| 2018 | 14 | |
| 2017 | 10 | |
| 2016 | 3 | |
| 2015 | 1 | |
| 2014 | 2 | |
| 2012 | 1 | |
| 2011 | 1 | |
| 2010 | 1 | |
| 2009 | 1 |
Where the attacks came from
An attack reaches a computer through something that people install. This is how the 124 attacks arrived.
- vendor binary41 attacks
- npm31 attacks
- browser extension14 attacks
- PyPI13 attacks
- source tarball6 attacks
- IDE extension5 attacks
- RubyGems4 attacks
- CI action3 attacks
- crates.io2 attacks
- other2 attacks
- Maven1 attack
- NuGet1 attack
- install script1 attack
Attacks on AI coding tools
5 attacks in the library went after AI coding tools. They ran inside the tool, stole its settings and keys, or planted files that the tool runs. All of them are from 2026.
- Claude Code extension backdoor on the Cursor Marketplace, 29 Oct 2026
- LiteLLM 1.107.0 PyPI and Docker compromise, 21 Oct 2026
- OVHcloud CLI GitHub release swap, 19 Oct 2026
- Tensorlake npm SDK Shai-Hulud compromise, 8 Oct 2026
- @apexacc/cli Defender-blinding C2 loader, 17 Sep 2026
The attacks we found first
@apexacc/cli, 2026
A founder's AI tool gained the ability to turn off Windows Defender and Smart App Control from a hidden administrator window, then take orders from a server. We found it before any security database had it. Read advisory VIGI-001-2026.
pystr-codec, 2026
A small codec package gained a file that runs at every Python start, downloads a JavaScript runtime and runs a hidden worm that steals tokens and republishes itself. We found it before any security database had it. Read advisory VIGI-002-2026.
How we count
An attack goes in the library when a public report or our own scan proves it. Each attack has its own page with its sources. The library shows a trend. It does not count every attack that happened.
FAQ
How many software supply chain attacks happened in 2026?
The Vigilance library holds 30 supply chain attacks from 2026, up to 31 Oct 2026. That is more than any earlier year in the library. In 2025 it holds 20.
Are supply chain attacks going up?
In the library, yes. 63 of the 124 attacks happened in the last three years, 2024, 2025 and 2026. The library counts attacks with a public report or our own scan, so it shows a trend and not a full count.
Do supply chain attacks go after AI coding tools?
Yes. 5 attacks in the library went after AI coding tools such as Claude Code and Cursor, all of them in 2026. They ran inside the tool, stole its settings and keys, or planted files that the tool runs.
See what your staff's AI tools bring in.
Vigilance checks each package that AI tools and your staff add to each computer. On a paid plan it swaps a bad update for the last safe version.