GitHub has shipped multiple security improvements to npm and GitHub Actions targeting supply chain attack techniques. Key changes include: npm's 72-hour read-only mode for high-impact accounts after sensitive changes, safer pull_request_target defaults to prevent pwn requests, read-only Actions cache for untrusted triggers, staged publishing for npm requiring additional 2FA approval, npm v12 disabling install scripts by default, Dependabot's new 3-day cooldown before opening version update PRs, CircleCI support for npm trusted publishing, an Actions network firewall in technical preview, and expanded self-service credential revocation APIs. These mitigations address the full attack chain from initial compromise through credential exfiltration and malware propagation.
Table of contents
Anatomy of supply chain attacksInitial compromiseExfiltrate credentialsPropagating the attackIdentifying and responding to supply chain attacksWhat’s Next?Tags:Written by4.7K Impressions1 Comment