Most GitHub Actions compromises do not start with a zero-day. They start with configuration: a tag that can be re-pointed, a token with more power than the job needs, a helpful workflow that checks out a fork's code "just to run the tests." The patterns are well understood, and every one of them is greppable. Below are the six risk classes that matter most, how to find each in your own repo, and the fix pattern for each. Run the commands in order — credential-holding release and deploy workflows first, because that is the order an attacker would walk.
1. Actions pinned to movable tags instead of full-length SHAs
A reference like actions/checkout@v4 points at a tag, and tags can be moved. If the account or repo behind a widely used action is compromised, the attacker re-points the tag and your next run executes their code — with your workflow's token and secrets in scope.…