TLDR Tech / InfoSec
GitHub Actions Cache Poisoning is eating open source
GitHub Actions cache poisoning lets attackers write poisoned dependency caches that later run inside high‑privilege publish workflows, as seen in the Angular, tj-actions, Cline, and TanStack incidents. Attackers either get a privileged workflow to write a malicious cache entry directly or evict and replace legitimate entries using tools like Cacheract. The recommendation is to audit everything related to pull requests, then disable or isolate caches in release jobs, pin actions to SHAs, gate workflow edits with CODEOWNERS, enforce non‑SMS 2FA, enable install cooldowns, and treat AI agent configs as executable code. If a compromised package has already run, remove the gh-token-monitor watcher on Linux and macOS before rotating any credentials, then reimage the affected hosts and rotate all secrets those machines can access.
Read the full story