Topic
Workflow trigger privileges, fork pull request handling, and token exposure in GitHub Actions.
Two compromised maintainer accounts pushed a GhostAction workflow into 346 GitHub repositories on Oct. 8, according to Socket's research team. GitGuardian, which named the campaign, is still reviewing the wave against its own data.
Reality
GhostAction's credential-stealing GitHub workflow has reached tens of thousands of repositories through more than 500 accounts since October 7, Socket says. Any repository carrying the file should be treated as having lost its Actions secrets and every key in its git history.
Reality
Scanner authors writing on dev.to hand-checked 60 public pull_request_target workflows and judged 6 exploitable by anyone who can open a pull request. About as many looked dangerous and were safe, so an audit has to read what runs after the checkout.
Reality
GitHub's workflow execution protections went generally available on September 17, and the evaluate mode that shows what a rule would block before enforcement is documented as an Enterprise Cloud capability.
Reality
Pinning a workflow to a commit SHA stops the tag moving under you, and resolving all 31 from the upstream repositories turned up an action whose v3 tag stopped moving at all while its releases reached v5.0.0.
Reality
GitHub gives forked pull requests a read-only token and no secrets, so any test that needs a credential fails. The two documented ways around that differ in whose code the secrets-bearing job actually checks out.
Reality
For anyone running pull_request_target, pinning v7 starts with a workflow audit rather than a version bump, and the credential relocation underneath it carries a runner version floor that self-hosted fleets should check first.
Reality