GhostAction campaign compromises 500+ GitHub accounts to steal cloud and AI keys
- Severity
- High
- Sources
- 1
What happened
GhostAction has expanded to over 500 hijacked GitHub accounts, with OpenSourceMalware counting 790 repositories carrying the workflow through 9 October 2026. Malicious security-audit.yml commits ("Add/Update security audit workflow") target repositories' default branches and use fetch-depth: 0 to harvest secrets from the full history, including two-line context around AWS key IDs to rebuild key pairs; exfiltration goes to 193.32.204[.]199. Defenders should rotate every secret named in the file, revoke and reissue affected tokens, scan history (git log -p --all), review CloudTrail for new IAM activity, revoke maintainer sessions and OAuth grants, block the IP at egress including self-hosted runners, and enable secret scanning with push protection.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Open .github/workflows/security-audit.yml, list the secret names it uses, and rotate every one of them.
- Scan the full git history with git log -p --all and rotate any keys found, even if they no longer appear in current files.
- Revoke all sessions, tokens, OAuth grants and SSH keys for any affected maintainer account, and turn on phishing-resistant multi-factor login.
- Block 193.32.204[.]199 in egress logs, including self-hosted runners.
Written by AI from the sources, checked against them