Gheist campaign uses stolen GitHub tokens to extract repository secrets

The Gheist campaign is using stolen GitHub tokens to steal secrets from developer repositories. Attackers plant workflows that print repository secrets into GitHub Actions logs, download the logs, and then delete the runs. The attacks have succeeded in private repositories and GitHub Enterprise environments. The campaign is described as ongoing and has harvested credentials and sensitive data from thousands of repositories.

AI-written summary, checked against the cited sources. How summaries work

Image: Dark Reading

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

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

  1. 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…

  2. Dark Reading

    '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.