CI/CD Pipeline Security Under Attack: Thousands of GitHub Accounts Compromised in 'wfx-loot' Campaign

A sophisticated supply-chain attack, dubbed 'wfx-loot', has compromised thousands of GitHub accounts, leading to the silent exfiltration of CI/CD secrets, cloud tokens, and IAM credentials from over 1,800 organizations. The attackers leveraged 4,837 previously stolen GitHub credentials to probe over 61,000 repositories for write access. Once write access was confirmed, a 1,500-line credential-stealing shell script was injected into GitHub Actions workflows. This script was designed to harvest a wide array of credentials, including AWS, Azure, and GCP credentials, OIDC tokens, and API keys for AI services like OpenAI, Anthropic, and Google's Gemini. The malicious code then exfiltrated compressed data and erased its traces within minutes, making detection challenging. This incident is a stark reminder that CI/CD pipelines have become a prime target for attackers. The "wfx-loot" campaign demonstrates a maturing playbook where adversaries weaponize trusted CI/CD pipelines to bypass traditional perimeter controls. The attack's ability to escalate cloud privileges by exchanging OIDC tokens for long-lived IAM credentials, and its targeting of agentic AI credentials and Kubernetes service-account tokens, significantly expands the potential blast radius of a single compromised workflow. This directly impacts any organization relying on GitHub Actions for their CI/CD, particularly those with multi-cloud deployments or those integrating AI services into their development workflows. This attack fits into a broader, well-established trend of increasing supply chain attacks and the weaponization of CI/CD environments. Previous incidents, such as the 2025 GhostAction attack, have highlighted the vulnerability of CI/CD pipelines. The industry has been increasingly focused on CI/CD security best practices, emphasizing treating pipelines as production infrastructure, implementing least-privilege access, and securing the software supply chain. However, the "wfx-loot" campaign underscores that even with awareness, the execution of these practices remains a significant challenge. The shift towards AI-driven development and the increasing use of AI services within CI/CD pipelines also introduces new attack surfaces, as evidenced by the targeting of AI service API keys. In practice, this means that organizations must immediately re-evaluate their CI/CD security posture. Practitioners should prioritize rotating all secrets and tokens that could have been exposed, especially for repositories that received suspicious pull requests or commits. Implementing stringent egress controls and anomaly detection on workflow-generated cloud traffic is crucial to prevent silent exfiltration. Furthermore, adopting a zero-trust approach within CI/CD, where every action and identity is verified, is no longer optional. This includes enforcing least-privilege access for all pipeline components, pinning third-party dependencies to immutable references, and signing and verifying all build artifacts. Organizations should also invest in continuous monitoring and auditing of CI/CD logs for any unusual activity, as the attackers in this campaign actively deleted workflow runs and logs to evade detection.