Loading story…
Open-source package registries that underpin software supply-chain security—PyPI, npm, Crates.io, RubyGems, and Maven Central—are facing a growing financial crisis that threatens their ability to operate securely. Michael Winser, co-founder of the Linux Foundation’s Alpha-Omega initiative, warned that registry usage is growing exponentially while investment in infrastructure and staffing remains flat, leaving these services “living on borrowed time.” Key cost drivers cited include bandwidth, storage, compute, and the expanding effort required to detect and remove malicious packages, with AI contributing to increased volume and velocity of submissions.
Both reports emphasize that current funding models (grants, donations, and in-kind support) are not keeping pace with operational and security needs, creating risk that registries will be unable to implement or sustain critical protections such as malware detection and package integrity controls—undermining “trusted source” assumptions central to SBOM-driven supply-chain programs. Winser argued that enterprises should normalize paying for registry services as an operational expense rather than treating support as optional charity; without more sustainable funding, the time-to-remediate malicious packages (reported as a median of ~39 hours in one account) and the overall exposure to supply-chain compromise are likely to worsen.
Trace attribution and downstream blast radius.
4 events from the most recent confirmed update back to the earliest known activity.
Winser argued that common monetization approaches such as charging for bandwidth, subscriptions, or publisher fees were unlikely to be sustainable and could fragment ecosystems. He said companies should instead normalize paying for registry operations and security as a standard business expense rather than relying on grants and donations.
At FOSDEM 2026, Michael Winser of Alpha-Omega said major open-source registries were financially strained as usage grew exponentially while infrastructure and staffing investment remained flat. He warned that underfunded security, not just hosting and bandwidth, posed the main risk to the software supply chain.
Across open-source ecosystems, registries detected 845,000 malicious packages from 2019 through January 2025. The reported median removal time was 39 hours, underscoring the risk that malware can spread before takedown.
In 2025, Alpha-Omega reviewed large open-source package registries including PyPI, npm, Crates.io, RubyGems, and Maven Central, finding that bandwidth was the largest cost category, with significant spending also required for storage, compute, and malware response. The review concluded that security work and new feature development were constrained by flat funding despite growing usage.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Open-source software supply chain risk continued to escalate, with reporting citing **454,600+** newly identified malicious packages across major repositories (including **PyPI, npm, Maven Central, NuGet, and Hugging Face**) and tactics ranging from **credential theft** to **multi-stage attacks** and even early **self-replicating** package malware. The activity reportedly concentrated heavily in **npm**, including high-volume “ecosystem flooding” (e.g., single accounts publishing **150,000+** malicious packages in days) and **hijacking of trusted projects**, exploiting developer reliance on superficial trust signals such as package names, READMEs, and download counts. Separately, researchers disclosed **“PackageGate”** vulnerabilities in JavaScript package managers (**npm, pnpm, vlt, and Bun**) that can bypass common post-incident defenses—namely `--ignore-scripts` and lockfile integrity—enabling malicious code execution via compromised dependencies. Koi Security reported six issues; **pnpm, vlt, and Bun** shipped fixes, while **npm** reportedly treated the behavior as expected. In parallel, threat actors abused **GitHub’s fork architecture** to distribute a spoofed *GitHub Desktop* installer promoted via search ads; execution deployed **HijackLoader** and established persistence via a **scheduled task**, underscoring that supply chain threats extend beyond package registries into developer tooling distribution channels.
Jun 29, 2026
Security researchers have identified a significant increase in destructive malware embedded within open source packages across major ecosystems such as npm, PyPI, NuGet, Go modules, and Docker Hub. Unlike financially motivated threats like cryptominers or credential stealers, these malicious packages are designed to inflict operational damage by deleting source code, wiping repositories, breaking builds, or sabotaging developer environments. Attackers often disguise these packages as legitimate developer tools or utilities, leveraging trusted registries to maximize reach and impact. The destructive payloads are frequently delayed or remotely controlled, allowing threat actors to time their attacks for maximum disruption while evading early detection. In CI/CD environments, a single compromised dependency can propagate rapidly, amplifying the operational fallout before the threat is identified and contained. Recent research highlights that Docker Hub, a widely used container registry, has also become a vector for supply-chain attacks, with malicious images distributed at scale to facilitate cryptomining and potentially more destructive activities. These campaigns exploit the implicit trust developers and organizations place in public registries, as well as the automated nature of modern software pipelines. Security teams are urged to extend supply-chain security controls beyond source code to include container images and other artifacts, as attackers continue to innovate in their methods for infiltrating and sabotaging software development and deployment workflows.
Jun 29, 2026
Major open-source software (OSS) foundations and public code repository stewards have issued a joint statement urging commercial software companies to provide sustainable financial support for the platforms they rely on. The statement highlights the critical role that OSS platforms play in the global software supply chain, with public code registries now handling trillions of downloads each month, much of it driven by automated commercial processes such as continuous integration pipelines and dependency scanners. The stewards, representing organizations including Alpha-Omega, the Eclipse Foundation, the OpenJS Foundation, OpenSSF, Packagist, the Python Software Foundation, the Rust Foundation, and Sonatype, warn that the current model—where large commercial users extract significant value without proportional financial contribution—threatens the long-term viability of these registries. They argue that open-source infrastructure cannot be expected to operate indefinitely on the basis of unbalanced generosity and informal, inconsistent support. The call to action comes in the wake of a series of high-profile attacks targeting OSS infrastructure, underscoring the urgent need for robust funding to enhance software supply chain security. The joint statement emphasizes that sustainable funding models must scale with usage, ensuring that the largest beneficiaries of OSS platforms contribute to their maintenance and security. The stewards point out that the explosion in OSS usage has not been matched by a corresponding increase in financial support, creating a risk of crisis for the ecosystem. They stress that the security of the global software supply chain is directly tied to the health and sustainability of OSS infrastructure. The statement also notes that commercial and proprietary software publishers often use public registries as free content distribution networks, further increasing the operational burden on these platforms. The foundations call for a shift in mindset among commercial users, urging them to recognize their responsibility in supporting the infrastructure that underpins their products and services. They highlight the need for new funding mechanisms that are predictable, scalable, and aligned with the level of usage. The statement concludes by warning that without committed financial support from the ecosystem’s largest users, the OSS ecosystem faces a growing risk of instability and security vulnerabilities. The call for action is seen as a pivotal moment for the future of open-source software and the security of the broader technology landscape. Industry observers note that this appeal may prompt a reevaluation of how commercial entities engage with and support the OSS community. The move is widely regarded as essential to ensuring the continued innovation, reliability, and security of open-source platforms that are foundational to modern software development.
Jun 29, 2026