Supply chain attacks hit hundreds of open source projects in the past year by chaining weaknesses across package repositories and CI/CD systems. GitHub has shipped a specific set of mitigations across npm and GitHub Actions, documented here in full technical detail. The changes target four distinct phases of the attack lifecycle: initial compromise, privilege escalation, credential exfiltration, and malware propagation.
The most immediately disruptive changes shipped in June 2026. High-impact npm accounts now enter a 72-hour read-only lockdown when an email change or 2FA recovery code is used, buying maintainers time to respond to phishing-driven takeovers. The default behavior of actions/checkout was changed to block untrusted fork code from executing in pull_request_target workflows, closing one of the most common CI/CD entry points. A separate fix restricts less-privileged workflows from writing to the shared Actions cache, which attackers previously used to poison credentials accessed by release and publishing workflows. CircleCI support for npm trusted publishing, added in April 2026, removes the long-lived credentials these attacks depend on exfiltrating.
The full post is worth reading for its precise breakdown of how each mitigation breaks a specific link in the attack chain, not just the feature announcements. A network egress firewall for Actions is currently in technical preview, logging all outbound traffic to surface credential exfiltration attempts, with blocking policies planned next. Staged npm publishing, added in May 2026, requires explicit 2FA approval before a newly published package reaches users, even if an attacker already has valid credentials. The architecture here is a layered defense model, and GitHub is naming exactly which attack techniques each control defeats.
[READ ORIGINAL →]