Skip to content
Supply-Chain Vulnerability Exposes 1,500 npm Packages to Malicious Takeover

Supply-Chain Vulnerability Exposes 1,500 npm Packages to Malicious Takeover

First seen 13 Oct 2026, 13:29 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 13, 2026 at 15:32 UTC
  • •Over 1,500 npm packages are vulnerable to malicious takeover due to a supply-chain flaw.
  • •AI agents are autonomously installing packages, increasing the risk of exposure to malicious code.
  • •The vulnerability was exploitable for four months after its initial disclosure.

Bloom Security's research reveals a supply-chain vulnerability in npm Trusted Publishing, affecting over 1,500 packages with more than 10 million downloads. The vulnerability allows attackers to publish malicious versions of legitimate packages by reclaiming abandoned GitHub repository addresses. AI coding agents, which autonomously install packages, exacerbate this risk by potentially installing malicious code without developer oversight. The investigation, named SlugFest, found that AI agents on developer machines can install up to 350 packages monthly. This vulnerability was exploitable for four months after its disclosure, during which time more packages became vulnerable. Bloom Security reported blocking a customer's AI agent attempting to install a vulnerable package, highlighting the real-world implications of the research. The flaw stems from npm's initial trust establishment method, which relied on human-readable repository addresses rather than permanent identifiers.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-13
Bloom Security publishes research
Bloom Security disclosed a vulnerability in npm Trusted Publishing affecting over 1,500 packages.
Hackernoon
2026-10-13
SlugFest investigation findings released
The SlugFest investigation revealed the extent of the vulnerability and its impact on AI agents.
bloom.security

More articles in this cluster (2)

Extracted Entities (6)

1 / 2

Common questions

How many npm packages are affected?
Over 1,500 npm packages are identified as vulnerable to exploitation.
What is the nature of the vulnerability?
The vulnerability allows attackers to publish malicious versions of legitimate packages by reclaiming abandoned GitHub repository addresses.
What should developers do to mitigate this risk?
Developers should review their dependencies and monitor for any unauthorized package installations by AI agents.