Cybersecurity Tech Brief By HackerNoon
Bloom Security Found a Supply-Chain Vulnerability Exposing 1,500 npm Packages to Malicious Takeover
Oct 14, 2026 · 7 min · 8 segments
This story was originally published on HackerNoon at…
Cybersecurity Tech Brief By HackerNoon
Oct 14, 2026 · 7 min · 8 segments
This story was originally published on HackerNoon at…
AI coding agents are changing how software gets built, but their growing autonomy is also creating new challenges for software supply chain security.
Tools that automatically select, install, and run dependencies can introduce packages into development environments without the same manual scrutiny traditionally associated with software installation.
Research from Bloom Security highlights how this shift intersects with a vulnerability in NPM-trusted publishing, potentially allowing attackers to publish malicious versions of legitimate packages by reclaiming abandoned GitHub repository addresses.
The investigation, dubbed Slugfest, identified more than one thousand five hundred vulnerable NPM packages with over ten million combined downloads, demonstrating how a relatively narrow weakness in a publishing mechanism could create a broader supply chain risk.
Bloom Security studied the behavior of millions of AI agents across large enterprises and found that the average endpoint receives approximately seventy agent-installed packages per month.
On developer machines, the number can approach three hundred fifty monthly installs.
These figures represent direct package installations and exclude the dependencies those packages bring with them.
The research found that individual agents install between zero point three and one point two packages daily, depending on the agent type.
Developer machines can see two to three installations per day, while a typical endpoint runs three AI agents across command line interfaces, integrated development environments, extensions, and assistants.
Developer machines may run five or more.
This activity changes the conditions under which software supply chain attack scans spread.
A malicious package no longer necessarily needs to persuade a developer to install it manually.
If an AI coding agent selects the package as a dependency, it may install and execute the code with limited human involvement.
Bloom also reported catching and blocking a customer's AI agent that attempted to install a package vulnerable to the issue.
The incident illustrated how the exposure described in the research could intersect with actual package installation activity.
AI coding agents are changing how software gets built, but their growing autonomy is also creating new challenges for software supply chain security.
Tools that automatically select, install, and run dependencies can introduce packages into development environments without the same manual scrutiny traditionally associated with software installation.
Research from Bloom Security highlights how this shift intersects with a vulnerability in NPM-trusted publishing, potentially allowing attackers to publish malicious versions of legitimate packages by reclaiming abandoned GitHub repository addresses.
The investigation, dubbed Slugfest, identified more than one thousand five hundred vulnerable NPM packages with over ten million combined downloads, demonstrating how a relatively narrow weakness in a publishing mechanism could create a broader supply chain risk.
Bloom Security studied the behavior of millions of AI agents across large enterprises and found that the average endpoint receives approximately seventy agent-installed packages per month.
On developer machines, the number can approach three hundred fifty monthly installs.
These figures represent direct package installations and exclude the dependencies those packages bring with them.
The research found that individual agents install between zero point three and one point two packages daily, depending on the agent type.
Developer machines can see two to three installations per day, while a typical endpoint runs three AI agents across command line interfaces, integrated development environments, extensions, and assistants.
Developer machines may run five or more.
This activity changes the conditions under which software supply chain attack scans spread.
A malicious package no longer necessarily needs to persuade a developer to install it manually.
If an AI coding agent selects the package as a dependency, it may install and execute the code with limited human involvement.
Bloom also reported catching and blocking a customer's AI agent that attempted to install a package vulnerable to the issue.
The incident illustrated how the exposure described in the research could intersect with actual package installation activity.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
