
Attackers Bypass GitHub Actions SHA Pinning Using Fork Impostor Commits in Supply Chain Attacks
Pinning GitHub Actions to exact commit SHAs has long been considered a strong defense against supply chain threats, yet attackers have already developed techniques to circumvent it. In March 2026, the group that compromised the Trivy scanner inserted malicious code disguised as an official GitHub checkout action update, complete with a security-fix label. The same fork-sharing method was later used against actions-cool/issues-helper, resulting in credential theft from affected pipelines. While SHA pinning prevents tag movement, it cannot verify authorship or confirm that a commit originates from the upstream repository rather than a fork. GitHub’s new workflow lockfiles, generally available since October 2026, add deterministic dependency locking and require commits to exist on source-repository branches, but they still leave runtime image builds and commit provenance unaddressed. An upcoming webinar led by Erika Heidi of Chainguard will examine these remaining gaps and recommend additional controls such as vetted action catalogs.
The Hacker NewsNov 17, 2026Translated from English