GitHub Hardens npm, Actions Against Attacks

GitHub is tightening its defenses against increasingly prevalent supply chain attacks targeting its npm package registry and GitHub Actions CI/CD platform. The move comes as bad actors increasingly exploit weaknesses in open source ecosystems to spread malware and steal sensitive information.

The company detailed a series of updates designed to disrupt common attack techniques, which often chain together vulnerabilities in package repositories and build systems. These efforts build on previous announcements aimed at securing the software supply chain.

Disrupting Initial Compromise

Attacks frequently begin by compromising a single project or its maintainers. To counter this, GitHub has implemented preventive account protection for high-impact npm accounts. These accounts enter a 72-hour read-only state following significant changes like email updates or 2FA recovery, providing maintainers time to regain control.

For GitHub Actions, the default behavior of the `actions/checkout` command has been altered. It now prevents the checkout of untrusted code from forks in pull request workflows unless explicitly opted out, addressing a common vulnerability in CI/CD pipelines. This change also extends to older versions of the action.

Granular control over who and what triggers GitHub Actions workflows is also being introduced. Enterprises, organizations, and repositories can now set policies to limit workflow execution to authorized users and trigger types, enforcing least-privilege principles and reducing the attack surface.

Furthermore, read-only caching for untrusted triggers in GitHub Actions aims to prevent attackers from escalating privileges by poisoning cache entries shared across workflows. This closes a common path for turning limited vulnerabilities into widespread credential compromises.

Securing Credentials and Propagation

Once initial access is gained, attackers focus on exfiltrating credentials. GitHub's trusted publishing for npm now supports CircleCI, enabling more users to authorize publishes without relying on long-lived CI/CD credentials. This directly removes a prime target for credential theft.

An Actions network firewall, currently in technical preview, will log outbound network traffic, allowing detection of malicious activity like unauthorized code downloads or credential exfiltration to new domains. Future iterations plan to enable network egress restrictions to block such attacks proactively.

To hinder the propagation of compromised packages, npm's staged publishing feature is being enhanced. This opt-in control requires additional approval and 2FA authentication before a package version is officially published, decoupling CI/CD credentials from registry publishing capabilities. This makes it significantly harder for compromised automation to distribute malware.

Upcoming breaking changes in npm v12 will disable install-time scripts by default. These scripts have been a vector for attackers to exfiltrate credentials during package installation, bypassing runtime execution. This change aims to cut off another avenue for immediate credential harvesting.

These cumulative updates represent a significant push by GitHub to fortify the open source ecosystem against the ever-evolving threat of npm supply chain attacks and bolster GitHub Actions security, aligning with broader industry efforts in DevSecOps best practices.