Defending Against Software Supply Chain Attacks Exploiting GitHub Actions' pull_request_target

Software supply chain attacks continue to pose a significant threat, with groups such as TeamPCP actively exploiting CI/CD pipelines to distribute malicious software. A key vector for these attacks involves the `pull_request_target` trigger within GitHub Actions. This specific trigger, designed to allow repository maintainers more flexibility in handling pull requests from forks, runs actions directly against the original repository rather than the forked version. While intended for legitimate purposes like maintenance automation and integration testing, this functionality inadvertently exposes workflows to potential compromise. The core of the vulnerability lies in the access tokens often required by these workflows. When `pull_request_target` is used, the workflow gains access to tokens that reside within the main repository's environment. If these tokens are long-lived and broadly scoped, they become prime targets for malicious actors. TeamPCP, for instance, has leveraged such access to deploy credential-stealing malware, siphoning off package registry tokens, cloud credentials, SSH keys, Git credentials, and personal access tokens from compromised CI/CD environments. To defend against these sophisticated attacks, several crucial steps are recommended. Firstly, security teams should audit all GitHub Actions workflows and remove the `pull_request_target` trigger if its functionality is not strictly required. Limiting its use reduces the attack surface significantly. Secondly, a robust defense mechanism involves SHA pinning for GitHub Actions. Workflows typically point to dependencies using version tags, which are mutable. If a maintainer's account is compromised, a workflow could be modified to reference a malicious version of a dependency. SHA pinning, where a specific hash for the dependency is specified, ensures that the exact, verified version of an action is always used, preventing unauthorized alterations. Finally, protecting developer and maintainer accounts is paramount. Open-source project maintainers are frequently targeted, making their account security a critical component of supply chain defense. GitHub has supported passkey-based authentication since 2023, based on FIDO2/WebAuthn standards. Passkeys are cryptographically tied to a domain at enrollment, rendering them immune to lookalike phishing sites and significantly enhancing account security against credential theft. Implementing passkeys across development teams adds a vital layer of protection against these evolving threats.