Why it matters
Teams using GitHub should review repository workflows and CI secrets for unauthorized changes or exposure, particularly for repositories touched during the October 8–9 surge.
What we know
Confirmed by several sources
- GhostAction compromised about 1,900 GitHub accounts and targeted more than 30,000 repositories. — The New Stack, The Hacker News
- The campaign attempted to extract 3,174 secrets from CI in public repositories. — The New Stack, The Hacker News
- The campaign intensified on October 8 and 9, 2026. — The New Stack, The Hacker News
Reported by one source
- The malicious workflows targeted CI/CD secrets, cloud access keys and AI provider API keys, and used disguised security-workflow names. — The New Stack
- StepSecurity considered personal access tokens from credential dumps a likely source of the stolen credentials. — The New Stack
Open questions
- How attackers initially obtained the compromised GitHub credentials has not been confirmed. — The New Stack
Coverage 2 publishers
The Hacker NewsFirst report
GhostAction Compromises About 1,900 GitHub Accounts, Targets Over 30,000 Repositories
The credential-theft campaign known as GhostAction has ramped up, targeting more than 30,000 repositories across 3,000 users and organizations. The spike, according to GitGuardian, was observed on October 8 and 9, 2026. "This resulted from…
-
Hackers hijacked 1,900 GitHub accounts. Then they went after 30,000 repos.
Hackers accessed roughly 1,900 GitHub accounts, then used them to slip credential-stealing workflows into more than 30,000 repositories. The malicious GitHub Actions jobs targeted CI/CD secrets, cloud access keys, and AI provider API keys.…
Earliest report first. Articles stay on their publishers’ sites; each link opens the original.
