GitHub CI/CD Pipeline Compromised via 4,837 Stolen Accounts
Attackers hijacked thousands of GitHub accounts to deploy a secret-stealing payload across repositories. The breach targeted CI/CD environments to harvest cloud credentials.
TL;DR
- 4,837 GitHub accounts were compromised using stolen credentials.
- A CI secret stealer was deployed in at least 1,806 repositories.
- The attack aimed to extract cloud and API credentials from CI workflows.
- Security firm Aikido Security discovered and reported the campaign.
- Organizations should audit CI/CD pipeline permissions and credential usage.
In a large-scale supply chain attack, threat actors leveraged stolen credentials from 4,837 GitHub accounts to inject malicious code into continuous integration pipelines. The goal was to silently harvest sensitive cloud and API credentials stored within those environments. According to security researchers at Aikido Security, the stealthy operation affected more than 1,806 public and private repositories.
This incident underscores the risks associated with excessive permissions in automated workflows and highlights the importance of securing developer identities and infrastructure access. Organizations relying on GitHub Actions and similar CI/CD tools must now re-evaluate their exposure and harden their development pipelines against such credential-based intrusions.
How the Attack Worked
- Attackers gained access to 4,837 GitHub accounts through unknown means, possibly reused passwords or phishing.
- Using these credentials, they injected a malicious script into CI workflows of repositories where the accounts had write access.
- The script was designed to exfiltrate secrets, tokens, and cloud credentials used during the build process.
- At least 1,806 repositories were impacted, indicating a wide reach across various organizations and projects.
Implications for Developers and Teams
- CI/CD pipelines often have high-privilege access, making them attractive targets for credential theft.
- Excessive permissions granted to service accounts or personal access tokens increase the impact of such breaches.
- Organizations should enforce just-in-time access, rotate credentials regularly, and monitor anomalous activity in build systems.
- Multi-factor authentication (MFA) and strong identity governance can help prevent unauthorized account access.
- Teams should audit third-party integrations and ensure minimal privilege principles are applied throughout the DevOps lifecycle.
Sources
Sources
Security email updates
One digest email when we publish new security articles (TL;DR plus links to read more). Unsubscribe anytime from the message footer. See our Privacy Policy.