Attackers found a way to make GitHub leak secrets for them
They used stolen access tokens to add malicious GitHub Actions workflows to compromised repositories
Wiz tracked the campaign, called Gheist, across more than 850 compromised accounts and 13,500 malicious branches
The workflows were designed to print accessible secrets into GitHub Actions logs
To evade secret masking, the attackers encoded the values in Base32, making them look different from the original secrets
They then downloaded the logs and deleted the workflow runs, removing the most obvious evidence from the interface
But deleting a run doesn't erase copies of its logs that attackers have already taken
a stolen GitHub token can become a way to extract credentials from a repository's own automation
🚨 850+ compromised GitHub accounts. 13,500+ malicious branches.
Researchers uncovered 'Gheist,' an ongoing campaign using stolen tokens to plant GitHub Actions workflows that dump private repo secrets into logs.
Attackers download the logs, then delete the runs.
Details: