Open source supply chain attacks are no longer a fringe threat—they are the primary vector for breaching modern software development. In 2026, open source vulnerabilities per codebase doubled to an average of 581, while malicious open-source packages surged 73% in just one year. Yet most organizations treat open source as a solved problem, relying on implicit trust in package registries that are now functioning as active delivery channels for malware, credential theft, and remote code execution.
Key Takeaways
- Open source vulnerabilities per codebase doubled to 581 average in 2026; 87% of codebases contain at least one vulnerability
- Malicious open-source packages increased 73% in 2025; npm accounts for 90% of malicious activity
- GlassWorm attack deployed 72+ malicious extensions across VSX, GitHub, and npm since January 2026
- 65% of organizations experienced a software supply chain attack in the past year; 66% came via malicious packages
- 65% of open source vulnerabilities remain unscored by the National Vulnerability Database, delaying critical triage
How Open Source Supply Chain Attacks Exploded in 2026
Supply chain attacks tripled in the past year, but open source represents the fastest path to developer credentials and production systems. The 2026 Open Source Security and Risk Analysis (OSSRA) report found that 87% of codebases now contain at least one vulnerability, with 78% rated high-risk and 44% critical—meaning remote code execution is a real possibility. This is not a marginal problem. It is the baseline for modern software development.
The attack surface has expanded dramatically because open source registries are under siege. Attackers treat npm, PyPI, and other registries as delivery infrastructure, flooding them with synthetic traffic, spam, and malware to obscure their payloads. The GlassWorm campaign discovered in March 2026 exemplifies this strategy: attackers deployed at least 72 malicious extensions mimicking legitimate tools—linters, formatters, code runners, and AI tools like Clade Code—across Open VSX, GitHub, and npm, affecting 151 repositories in a single week. This is not opportunistic; it is coordinated, platform-agnostic, and designed to evade detection by blending into normal developer workflows.
The Scale Problem: Why npm Dominates Malicious Activity
npm accounts for 90% of detected malicious activity in open source registries, a staggering concentration that reflects both the registry’s size and the speed at which JavaScript-based attacks propagate. ReversingLabs’ 2026 Software Supply Chain Security Report documented a 73% increase in malicious open-source packages throughout 2025, with npm malicious activity doubling year-over-year. The first registry-native worm, Shai Hulud, demonstrated that attackers are now treating package registries not as distribution channels but as breeding grounds for self-propagating threats.
What makes this worse is the shift in targeting strategy. Attackers are no longer flooding registries with obscure typosquatted packages—they are hijacking legitimate, popular packages with established trust and large download volumes. If a package is downloaded millions of times monthly, compromising it once delivers malware to thousands of projects simultaneously. The economics are irresistible.
Open Source Supply Chain Attacks vs. Proprietary Software
Both open source and proprietary software are exploited through implicit trust in signed updates and vendor binaries, but open source bears the brunt because of scale, automation, and the ecosystem’s architectural assumption of trust. When you pull an npm package, you are executing arbitrary code with minimal friction. There is no gating layer, no mandatory security review, no human approval. Proprietary software requires a vendor to sign and release updates; open source requires only a developer with push access to a repository.
The 2026 OSSRA report revealed that 65% of organizations experienced a software supply chain attack in the past year. Of those, 66% were hit via malicious packages—either typosquatted imitations or hijacked legitimate ones—while 34% suffered compromises of already-legitimate packages. This distinction matters: typosquatting is a problem you can theoretically solve with better package management discipline. Hijacking legitimate packages is not. It requires the registry itself to be breached or a developer’s credentials to be stolen.
The Vulnerability Scoring Crisis
Here is a silent killer hiding in plain sight: 65% of open source vulnerabilities remain unscored by the National Vulnerability Database, the authoritative source for vulnerability severity assessment. Without a score, security teams cannot triage effectively. They cannot prioritize patching. They cannot justify remediation efforts to management. Vulnerabilities sit in codebases, unranked and unaddressed, waiting to be weaponized.
This creates a vacuum that attackers exploit. If a vulnerability has no NVD score, it has no urgency. If it has no urgency, it does not get fixed. Meanwhile, the vulnerability count per codebase has doubled, meaning the average organization is now managing twice as many unscored, unranked security gaps as they were a year ago.
AI Tooling as a New Attack Surface
Open source supply chain attacks are expanding into AI infrastructure. Malicious payloads are being embedded in model files and plugins, while unsanctioned external models are expanding the supply chain into uninspected layers. This is not hypothetical—it is already happening. As AI adoption accelerates, the attack surface grows faster than security tooling can defend it.
FAQ
What is the most common type of open source supply chain attack?
Malicious packages account for 66% of supply chain attacks, split between typosquatted imitations and hijacked legitimate packages. Typosquatting relies on developer mistakes; hijacking relies on credential theft or registry compromise. Both are equally damaging once deployed.
Why is npm so heavily targeted by attackers?
npm accounts for 90% of detected malicious activity because it is the largest open source registry by volume, JavaScript dominates web and backend development, and the ecosystem has historically prioritized speed over security friction. A single compromised package can reach millions of projects automatically.
How can organizations reduce their open source supply chain risk?
Audit dependencies regularly, implement Software Bill of Materials (SBOM) generation, monitor for known vulnerabilities, enforce code review for dependency updates, and restrict package registry access where possible. However, these are mitigations, not solutions—the fundamental problem is that open source registries operate on trust, and that trust is being systematically exploited.
Open source supply chain attacks have moved from edge case to baseline threat. The 2026 data is unambiguous: vulnerabilities are doubling, malicious packages are proliferating, and most organizations have no visibility into the code they are running. The blind spot is not in open source itself—it is in the false assumption that dependencies are secure by default. They are not. And until registries, tooling, and organizational practices catch up to the reality of coordinated, platform-agnostic attacks, the damage will only accelerate.
Edited by the All Things Geek team.
Source: TechRadar
