Skip to content
Gheist Campaign Exploits Stolen GitHub Tokens to Access Secrets

Gheist Campaign Exploits Stolen GitHub Tokens to Access Secrets

First seen 26 Oct 2026, 18:03 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 26, 2026 at 19:33 UTC
  • •Gheist campaign exploits stolen GitHub tokens to access sensitive repository secrets.
  • •Over 13,500 branches have been created across more than 850 compromised accounts.
  • •GitHub's new controls prevent malicious workflows in public repositories but not in private ones.

An ongoing automated campaign, dubbed Gheist, is exploiting stolen GitHub tokens to create malicious workflows that expose repository secrets in GitHub Actions logs. The campaign has affected over 850 accounts and resulted in the creation of more than 13,500 branches across various repositories, including private enterprise ones. Attackers utilize these tokens to plant workflows that print sensitive information into logs, which they then download before deleting the runs. GitHub has implemented controls that prevent malicious workflows in public repositories from executing without approval, but these protections do not extend to private repositories or GitHub Enterprise Server. Wiz, the cloud security company tracking the campaign, identified that the attackers have been cycling through user tokens and cloning repositories since September 15. As of October 24, two-thirds of the compromised accounts were no longer available on GitHub, likely due to responses from the platform. The campaign continues to evolve, posing a significant risk to organizations using GitHub.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-09-15
Gheist campaign tracked since
Wiz began monitoring the Gheist campaign, which exploits stolen GitHub tokens to access repository secrets.
The Hacker News
2026-10-24
Two-thirds of compromised accounts removed
Wiz reported that approximately two-thirds of the accounts involved in the Gheist campaign were no longer available on GitHub, likely due to response actions.
Infosecurity-Magazine

More articles in this cluster (3)

Following this threat?

Track Gheist and Amazon Web Services in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

How are GitHub tokens being exploited?
Attackers are using stolen GitHub tokens to create workflows that print repository secrets into logs, which they then download.
What protections does GitHub have in place?
GitHub has implemented controls that pause suspicious workflows in public repositories, but these do not apply to private repositories or GitHub Enterprise.
What should organizations do to protect themselves?
Organizations should rotate all secrets and revoke any compromised tokens immediately to mitigate exposure.