Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
npm supply chain attacks
- Objective
- Threat actors targeting software ecosystems, developer workflows, and trusted services via npm packages 1 source
A campaign of attacks targeting the npm package registry and its ecosystem. These attacks exploit the software supply chain by compromising or injecting malicious code into npm packages, which are then distributed to downstream developers and applications that depend on them.
The campaign targets the software supply chain 1 with low confidence based on available reporting.
npm supply chain attacks typically leverage the trust developers place in open-source packages. By poisoning popular or newly created packages, attackers can achieve broad code execution across organizations that install compromised dependencies. Attack vectors include account takeovers of package maintainers, typosquatting (registering packages with names similar to legitimate ones), dependency confusion (uploading higher versions to public registries), and direct malicious package publication.
The npm ecosystem's scale and the difficulty of auditing thousands of transitive dependencies make it an attractive target. A single compromised package can affect thousands of downstream projects automatically when they update dependencies.
Notable characteristics of npm supply chain campaigns include:
- Targeting both widely-used packages and niche dependencies
- Using obfuscation and delayed payload execution to evade detection
- Exfiltrating credentials, environment variables, or source code
- Installing cryptominers or backdoors for persistent access
Detection challenges include the volume of packages published daily, limited automated security scanning at the registry level, and the trust model that assumes maintainers are trustworthy. Organizations typically mitigate risk through dependency pinning, lock files, private registries, and automated vulnerability scanning tools.
Facts 2
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| First seen | 2026 disputed
also reported: 2026-09-29 (low)
|
low | 1 | 5 |
| Objective | Threat actors targeting software ecosystems, developer workflows, and trusted services via npm packages | low | 1 | 5 |
Target sectors 1
Neighbourhood
Targets 5
Frequently mentioned together 2
Sources 5
- Amazon ties DPRK hackers to axios and three other NPM attacks - Developer Tech News · Google News: Hacking
- Fake Express Packages on npm Spread a Linux Worm · Lobsters
- Stolen AI credentials feed growing LLM proxy economy · CSO Online
- short 🚨 #Researchalert: New npm supply chain attack. · Wiz
- Microsoft at Black Hat USA 2026: Defending trust in the age of AI and supply chain attacks · Microsoft Security Blog