The open-source package repository is the front line
„The npm, PyPI, and developer toolchains have become recurring targets for self-propagating worms and state-linked actors. A single compromised maintainer account or package organization can poison packages with weekly million-download volumes.”
Counter-narrative
Poisoned versions are detected and withdrawn quickly, with damage mostly limited to credential theft. None of the actors in the examined stories represent this, and the leak of Grafana source code contradicts it.
Voices
Wiz, Snyk, StepSecurity, FBI, Amazon/AWS, developer security press
Analysis
According to the narrative, the development environment and CI/CD have become the primary entry points leading to corporate cloud and developer secrets. This is fueled by campaigns appearing almost monthly between November 2025 and November 2026, including Shai-Hulud, TeamPCP, and those attributed to North Korea. Developer security companies have a direct market interest in this. There are hardly any weak points. At most, the damage in individual cases is rarely quantified, and attribution is often just a single company's assertion.
What's at stake: The stake is whether the trust model of open-source infrastructure remains sustainable without mandatory signing and authentication.
Narrative sub-threads
Recurring waves of self-propagating npm worms
Worms similar to the Shai-Hulud family have appeared in recurring waves on npm since November 2025. They steal credentials and spread via published packages. High-download packages are also infected: the Lightning and Intercom-client packages combined for 8.3 million downloads, while node-ipc was affected by more than 822,000 weekly downloads. A known payload reappeared after 111 days, evading scanners.
Here, the mechanism is automatic infection spreading from machine to machine and package to package, not a one-time targeted poisoning or state campaign.
→ lasting · evidence: strongState-linked developer-targeting campaigns
Campaigns primarily attributed to North Korean actors, and in one case Chinese actors, target developers. Their tools include malicious packages (in one campaign, a total of 1,700 packages across npm, PyPI, Go, and Rust repositories), fake recruitment and job projects, and hijacked update channels (in the case of Notepad++, for six months).
The actor is, according to attribution, a state or state-linked group. The mechanism involves social engineering (fake job interviews, recruiters) and mass lure packages. Attribution stems from vendor statements (Amazon/AWS) and media reports, not from official sources.
▲ at peak · evidence: strongHijacking of legitimate packages via CI/CD
Stolen tokens, breached organizational and maintainer accounts, and poisoned CI/CD workflows are used to distribute malicious code through widely used, legitimate package releases, in several cases credential stealers. Affected parties include LiteLLM (twice during the year), Trivy, AsyncAPI, dYdX, Telnyx, and the Microsoft agent framework.
It is not about bait packages, but about the takeover of trusted release chains (GitHub Actions, PyPI releases). Groups such as TeamPCP are linked to this, as are law enforcement steps: an FBI warning and the arrest of two alleged TeamPCP members.
↗ rising · evidence: moderatePoisoning of developer extensions and AI tools
The attack extends beyond package registries to code editor extension markets (Open VSX, VS Code, Cursor) and update servers (eScan). It also affects third-party AI tools used by developers: the Vercel incident was caused by the compromise of Context.ai.
The target surface is the IDE and extension ecosystem (VS Code, Open VSX, Cursor), software update infrastructure, and embedded AI tools, not the classic npm/PyPI packages.
Sub-thread stories
Recurring waves of self-propagating npm worms
State-linked developer-targeting campaigns
Hijacking of legitimate packages via CI/CD
Poisoning of developer extensions and AI tools
Who is affected and how
- security leader
- Include supply-chain risk in supplier assessments.
- security operations
- Monitor traffic exiting CI runners and anomalies in cloud key usage, as campaigns specifically target cloud and CI/CD credentials.
- developer
- Record dependency versions, disable installation scripts where possible, and replace publishing tokens with short-lived, OIDC-based authentication.
- business leader
- The leak of Grafana's source code shows that a compromised dependency can become a trade secret loss; therefore, budget for developer security is needed.
Hungary
None of the examined stories carry a [HU] marker, so the domestic footprint of the narrative is absent or minimal during the period.
Weekly trend
Turning points
Supporting stories
Machine analysis based on story titles and summaries, with a verification pass. The source of the facts is the article linked at each story.
What do you make of this piece?
The split shows after 20 votes.
Why? Your answer is not shown publicly; it helps the editors.