The classifier judged this item not relevant to AI security, so it is left out of lists, feeds, the API and dataset releases. If that is wrong, report a correction on this page.
Hardening GitHub Actions Against Outside Threats
- Published
- Record updated
Summary
The article argues that 2025 and 2026 supply chain attacks entered widely used packages through their release processes, which ran on GitHub Actions, rather than through typosquats or malicious new packages. It lists incidents including tj-actions/changed-files (March 2025), Nx s1ngularity (August 2025), trivy-action (March 2026), and LiteLLM 1.107.0 (October 2026). The post is part one of a series, covering outside threats such as pull requests, third-party actions and downloaded scripts.
Mitigation
Pin every action to a full commit SHA rather than a tag or branch, because Git tags are movable pointers, and adopt a workflow lockfile. Pinned-by-SHA repositories were unaffected in the tj-actions/changed-files incident, while tag-pinned ones executed the malicious code.