GitHub and npm Roll Out New Defenses Against Supply Chain Attacks

GitHub Security Lab has detailed a series of recent enhancements to its npm package manager and GitHub Actions platform, specifically engineered to thwart the growing threat of supply chain attacks. These improvements target common exploitation vectors used by attackers to compromise open-source projects and spread malware.

The strategy focuses on breaking critical links in the attack chain, acknowledging that no single solution can fully prevent these complex assaults. By studying prevalent attack patterns, GitHub has implemented measures to disrupt initial compromise, credential exfiltration, and the propagation of malicious code.

To counter initial compromise, npm now enforces a 72-hour read-only period for high-impact accounts undergoing email or two-factor authentication recovery processes. This delay provides maintainers crucial time to detect and respond to account takeovers. Concurrently, GitHub Actions has defaulted the actions/checkout action to a safer mode, preventing the execution of untrusted code from pull request forks, a common vulnerability known as "pwn requests."

Further bolstering CI/CD security, GitHub Actions now offers granular controls over workflow triggers. Enterprises, organizations, and repositories can define policies to restrict who can initiate workflows and which trigger types are permissible, enforcing a principle of least privilege. Additionally, cache access for untrusted triggers is now read-only, mitigating cache poisoning attacks that attackers use to escalate privileges.

To combat credential exfiltration, npm has expanded its trusted publishing support to include CircleCI, enabling more users to eliminate long-lived credentials from their CI/CD pipelines. GitHub Actions is also previewing a network firewall to log and potentially block suspicious outbound traffic, such as attempts to download malicious code or communicate with unauthorized domains.

For propagation control, npm's staged publishing feature, now opt-in, requires additional approval beyond CI/CD credentials before a package version can be published to the registry. This decouples the credentials used in automated workflows from the ability to distribute malicious code.

These updates represent a proactive, multi-layered approach to securing the software supply chain. By addressing specific, high-impact attack techniques, GitHub aims to significantly reduce the risk posed by malicious actors targeting the open-source ecosystem and CI/CD infrastructure.