Loading story…
GitHub is rolling out enhanced security controls for the npm registry after a series of high-profile supply-chain attacks. Key changes include mandatory two-factor authentication, deprecation of legacy tokens, shorter token lifetimes, and the adoption of trusted publishing workflows. These measures aim to mitigate risks from recent incidents that compromised thousands of accounts and packages.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
GitHub announced new npm security measures including stronger authentication requirements for publishers, expanded use of access tokens, and policy changes aimed at reducing phishing, account takeover, and malicious package publication. Multiple reports describe the move as a response to rising npm-focused attacks and the Shai-Hulud incident.
A supply-chain campaign dubbed Shai-Hulud emerged in the npm ecosystem, using malicious packages and related compromise activity that raised concern about software publishing security. Coverage describes it as a catalyst for broader scrutiny of npm account protection and package release integrity.
8 references tracked. Mallory keeps watching after this page renders.
techrepublic.com
Open sourcereversinglabs.com
Open sourcescworld.com
Open sourcetheregister.com
Open sourcego.theregister.com
Open sourcedarkreading.com
Open sourcehelpnetsecurity.com
Open sourcebleepingcomputer.com
Open sourceMap 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.
A series of high-profile supply chain attacks targeted the npm ecosystem, compromising hundreds of packages and exposing sensitive data. The s1ngularity attack exploited a vulnerability in GitHub Actions to steal npm publishing tokens for Nx packages, leading to the distribution of credential-harvesting malware and the public exposure of thousands of private repositories and secrets. Another incident involved a phishing campaign against a prominent npm maintainer, resulting in the compromise of widely used packages such as debug and chalk. These attacks highlighted the persistent risks posed by weak CI/CD protections, compromised dependencies, and social engineering tactics. In response to these incidents, GitHub implemented stricter security measures for npm package publishing. The new requirements include mandatory two-factor authentication (2FA) for all local publishing, limiting token lifetimes, and promoting trusted publishing workflows. Legacy authentication methods are being deprecated in favor of FIDO-based 2FA, and developers must now use hardware security keys, biometrics, or authenticator apps for authentication. These changes aim to reduce the risk of account takeovers and malware injection, but experts warn that additional security practices are necessary to address other attack surfaces within the software supply chain.
Jun 29, 2026
GitHub rolled out new supply-chain protections across **GitHub Actions** and **npm** to curb attacks that abuse CI/CD workflows and malicious package publishing. On public repositories hosted on GitHub.com, workflow runs that GitHub flags as suspicious are now automatically paused until a repository collaborator with write access approves them through an authenticated web session. The safeguard is enabled by default and is aimed at attacks involving compromised GitHub credentials, malicious workflow files, and workflow-based secret theft or package tampering, though GitHub has not disclosed detection logic and said the control does not guarantee every malicious run will be caught. GitHub also introduced **publish-time malware scanning** for npm packages, shifting enforcement from scanning after publication to gating releases before they become available. Under the new process, a package can be published, held for review, or blocked based on scan results, alongside new dual-use metadata requirements such as `contentPolicy` and `DISCLOSURE`. The changes build on GitHub’s broader response to open-source supply-chain attacks, including guidance to pin third-party Actions to full commit SHAs, avoid unsafe `pull_request_target` usage, use **OpenID Connect** for secretless authentication, and rely on trusted publishing across ecosystems including **npm**, **PyPI**, **NuGet**, **RubyGems**, and **Crates**.
Jul 31, 2026
GitHub has released **npm v12** with major supply-chain protections enabled by default, blocking lifecycle install scripts, implicit `node-gyp` rebuilds, Git dependencies, and remote URL dependencies unless users explicitly approve them. The change is aimed at reducing install-time code execution abused by recent npm malware campaigns, and introduces an allowlist-style workflow for trusted scripts. GitHub also began phasing out granular access tokens that bypass two-factor authentication: those tokens will lose sensitive account, package, and organization management capabilities starting in August 2026, and are set to lose direct publishing rights in a later phase, with maintainers encouraged to use trusted publishing via **OIDC** or staged publishing with human 2FA approval instead. **pnpm 11.10** shipped parallel hardening measures focused on preventing credential theft and unsafe build behavior in package workflows. The release adds a structured `_auth` setting that binds credentials to a specific registry URL and only reads them from global configuration or environment variables, blocking malicious project files such as `.npmrc` or `pnpm-workspace.yaml` from redirecting tokens to attacker-controlled hosts. It also stops forwarding upstream registry credentials to install-accelerator servers, restricts `pnpm deploy` and `pnpm pack-app` from writing outside the project, prevents repositories from substituting macOS code-signing tools, and fixes a prototype pollution issue involving a dependency named `__proto__`.
Aug 14, 2026