GitHub tightens npm and Actions security against supply chain threats
Open-source supply chain attacks are escalating. Over the past year, attackers have repeatedly exploited weaknesses in package repositories and CI/CD pipelines to push malware into hundreds of projects at once, often stealing credentials to spread further. To counter this, GitHub is rolling out layered security changes across npm and GitHub Actions designed to break the most common attack paths before they escalate.
Locking down maintainer accounts
One persistent entry point has been phishing campaigns that compromise maintainer accounts. Starting this month, npm is placing high-impact accounts into a 72-hour read-only mode whenever email changes or recovery codes are used—giving maintainers time to regain control before an attacker can publish malicious packages. “Pwn requests,” another favored vector, abuse GitHub Actions workflows that trigger on untrusted pull requests from forks. GitHub is now shipping safer defaults: actions/checkout will no longer automatically pull code from forks in risky triggers unless explicitly opted out after review. Older versions of the action are also receiving backports to close the same gap.
Policy levers for CI/CD governance
Beyond defaults, GitHub is adding enterprise, organization, and repository-level controls to restrict who—or what—can trigger workflows. Teams can now set policies that limit workflow execution to approved contributors or specific trigger types, reducing the attack surface available to malicious actors. These granular controls complement the safer defaults, giving organizations a way to enforce least-privilege even when custom workflows are required.
Why it matters
These measures directly address the two most common initial compromise techniques in recent supply chain campaigns—maintainer account takeovers and untrusted CI triggers. By slowing down account misuse and making risky workflow behaviors opt-in rather than automatic, GitHub raises the cost for attackers while giving maintainers and security teams more time to respond. For organizations relying on public repositories and CI pipelines, the changes shift the balance toward proactive defense without requiring wholesale rewrites of existing processes.
Source: GitHub Blog. AI-assisted editorial synthesis — TechnoExpress.