Most teams think about dependency risk in terms of CVEs, malware, and typosquatting. But there is another kind of supply-chain risk that can hit just as hard: a package you already trust can change its license in a later release, turning a
This weekly list covers the ten most significant malicious or compromised packages recently observed in public registries.
1. @builder.io/dev-tools (npm)
* Package: https://www.npmjs.com/package/@builder.io/dev-tools
* Severity: critical
* Affected versions: 1.65.0
* Downloads: 35136
* First seen:
This weekly list covers the ten most significant malicious or compromised packages recently observed in public registries.
1. puppeteer-core (npm)
* Package: https://www.npmjs.com/package/puppeteer-core
* Severity: critical
* Affected versions: 25.1.0
* Downloads: 18014723
* First seen: 2 June 2026 at
This weekly list covers the ten most significant malicious or compromised packages recently observed in public registries.
1. events-channel (npm)
* Package: https://www.npmjs.com/package/events-channel
* Severity: critical
* Affected versions: all
* Downloads: 39778
* First seen: 25 May 2026 at 16:42
Your NuGet packages are a bigger attack surface than your code.
Think about it: when was the last time you audited a dependency before running dotnet add package? You check the download count, maybe the GitHub stars, and move on. Meanwhile, you&
This weekly list covers the ten most significant malicious or compromised packages recently observed in public registries.
1. durabletask (pypi)
* Package: https://pypi.org/project/durabletask/
* Severity: critical
* Affected versions: 1.4.1-1.4.3
* Downloads: 386297
* First seen: 19 May 2026
There's a very normal point in a container setup where a service stops being “just a service” and starts dragging infrastructure concerns in behind it.
A Postgres container needs better log handling. A vendor image needs a reverse proxy in
GitHub Actions is one of the most convenient ways to automate builds, tests, releases, and deployments. It is also one of the easiest places to accidentally hand attackers a path into your software supply chain when workflow trust boundaries are too loose.