GitHub Launched npm Staged Publishing Security Feature
The new opt-in system requires manual 2FA approval for package releases to prevent malicious code injection.
Updated on Sept. 21, 2026 in Cybersecurity
Live Poll
Should software registries mandate human approval for code updates to improve security?
GitHub implemented a staged publishing feature in npm CLI version 11.15.0 on May 22, 2026. This security update introduces a mandatory 2FA checkpoint for package maintainers to verify new releases before they become publicly available.
Why it matters
This feature aims to mitigate automated supply chain attacks by closing the security gap between stolen credential usage and the deployment of malicious software. It provides a defensive layer against campaigns that previously leveraged CI/CD tokens to seed poisoned packages.
Staged publishing routes tarballs to a secure queue that necessitates interactive 2FA approval, preventing automatic deployment even when OIDC-based trusted publishing is utilized. This protocol functions within npm CLI version 11.15.0.
The players
GitHub
This subsidiary of Microsoft manages the npm registry and provides the core platform for open-source development.
TeamPCP
This is a malicious threat actor group identified in reports for executing supply chain attacks against software registries.
The details
The implementation follows high-profile incidents like the March 2026 compromise of the axios library, which saw 100 million weekly downloads exposed to theft. By requiring manual intervention, the registry restricts attackers who use stolen CI/CD tokens to seed malicious code across the ecosystem.
Timeline
March 2026: The axios library was compromised via maintainer account theft.
May 22, 2026: GitHub released npm CLI 11.15.0 featuring staged publishing.
September 2026: A report was published regarding the efficacy of npm security gates.
The Tech Race
This move represents a shift in the ongoing arms race between registry maintainers and supply chain attackers. It signals a move away from fully automated deployment pipelines to models requiring human-in-the-loop verification.
Developers and maintainers must now configure their publishing workflows to include an interactive 2FA step, which may add friction to automated deployment cycles. This change enhances protection for project integrity at the cost of additional manual verification time per release.
The takeaway
Maintainers should enable this feature to protect their projects from account takeover attacks that have historically exploited automated trust. Implementing manual checkpoints is now a critical practice for securing software supply chains against modern threat actors.
Further reading
Learn more about the latest industry standards for protecting development pipelines in the Cybersecurity section.
More information
View technical release notes and security updates on the Official GitHub Changelog.
Source note: This article includes information reported by GCN.
Live Poll
Should software registries mandate human approval for code updates to improve security?
