Why it matters
Teams using GitHub repositories, including private repositories and GitHub Enterprise, should review token exposure and repository secrets because the campaign has successfully extracted secrets through Actions logs.
What we know
Confirmed by several sources
- The Gheist campaign uses stolen GitHub tokens to target repository secrets. — Dark Reading, The Hacker News
Reported by one source
- Attackers plant workflows that print repository secrets into GitHub Actions logs, download those logs, and delete the runs; attacks succeeded in private repositories and GitHub Enterprise environments. — The Hacker News
- The campaign has harvested credentials and sensitive data from thousands of developer repositories. — Dark Reading
- Wiz analyzed the attacks. — The Hacker News
Coverage 2 publishers
The Hacker NewsFirst report
Gheist Uses Stolen GitHub Tokens to Steal Private Repository Secrets via Actions Logs
An automated campaign is using stolen GitHub tokens to plant workflows that print a repository's secrets into its GitHub Actions logs, which the attackers then download before deleting the runs. The attacks have succeeded in private…
-
'Gheist' Weaponizes GitHub Tokens to Steal Cloud Secrets
An ongoing supply chain attack is harvesting credentials and sensitive data from thousands of developer repositories.
Earliest report first. Articles stay on their publishers’ sites; each link opens the original.
