Gheist Campaign Harvests Secrets from GitHub Repositories
Original source
Gheist Uses Stolen GitHub Tokens to Steal Private Repository Secrets via Actions Logs
The Hacker News →Wiz has tracked the Gheist campaign since September 15, attributing attacks on over 850 GitHub accounts to a group using stolen tokens to plant malicious workflows. The tool creates branches named ci-sync- with random suffixes and commits a workflow that prints repository secrets into GitHub Actions logs, encoding them in base32 to bypass GitHub’s secret masking. The attackers then download the logs and delete the runs, leaving no trace on external servers.
The campaign has successfully targeted private repositories and GitHub Enterprise environments, accounting for more than 13,500 planted branches. GitHub’s automatic safeguard that pauses suspicious runs applies only to public repositories, leaving private repositories and GitHub Enterprise Server unprotected. Every public run Wiz examined was halted before execution, but private systems remain exposed.
The stolen tokens originated from infostealer logs and earlier supply-chain attacks, including the March compromise of the Trivy vulnerability scanner. As of October 24, the campaign continued operating with evolving techniques, including a variant targeting self-hosted runners. Wiz advises affected repositories to rotate all accessible secrets and credentials, revoke compromised tokens, and search audit logs for the distinctive ci-sync- branch pattern.
Read the full article
Continue reading at The Hacker News →This is an AI-generated summary. Read the original for the full story.