العربية
🚨 BreakingFBI Warns Artex AI Tool Automates Hacks at Machine Speed

CI Secret Stealer Hits 1,800+ GitHub Repos via Stolen Accounts

Security World Teamاقرأ بالعربية

An attacker used 4,837 stolen GitHub accounts to plant code that steals CI secrets and cloud credentials; it ran in at least 1,806 repositories.

Illustration for Breaking Security Alerts
Illustration by Security World

⚡ Why it matters

If your repositories hold cloud keys or deployment tokens in GitHub Actions, they may be exposed even if your own account was not hijacked, because any collaborator with write access could be a victim.

According to Aikido Security, an attacker began using stolen credentials for 4,837 GitHub accounts last Tuesday, planting secret-stealing code in repositories those accounts could write to.

The code was built to steal the secrets and cloud credentials available to the repository's continuous integration (CI) pipelines, and it ran in at least 1,806 repositories, meaning the attacker likely collected secrets from many of them.

What to do now

  1. Review the commit history and .github/workflows files in your repositories for changes you did not make.
  2. If you find any suspicious change, treat every secret your CI pipelines can access as exposed and rotate it immediately.
  3. Require two-factor authentication with security keys for all team members, and reduce the number of people with write access.
  4. Use OIDC instead of long-lived cloud keys in GitHub Actions, and restrict GITHUB_TOKEN permissions.

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories