Security Firm Aikido Security Discloses 'wfx-loot' Attack: Over 4,800 Compromised GitHub Accounts Used to Steal Cloud and AI Credentials
Aikido Security disclosed a large-scale GitHub credential theft campaign where attackers used stolen tokens to modify Actions workflows, stealing AWS, Azure, and OpenAI API keys.
Cybersecurity firm Aikido Security disclosed a large-scale GitHub credential theft campaign codenamed "wfx-loot" on November 12. The activity began on November 10, with attackers using stolen GitHub access tokens to compromise 4,837 accounts and probe write permissions across 61,764 code repositories. According to Aikido's statistics, at least 1,835 repositories executed malicious programs.
Unlike previous incidents, this attack did not exploit software vulnerabilities in GitHub Actions itself. Instead, attackers impersonated compromised accounts to create pull requests, confirming write access before modifying GitHub Actions workflows or injecting malicious shell scripts. Because some compromised accounts held collaborator or organization-level access across multiple projects, the attack expanded laterally to other development teams' repositories.
When the modified workflows ran, the malware collected sensitive data from the CI/CD environment, including GitHub tokens, cloud service credentials for AWS, Google Cloud, and Microsoft Azure, as well as API keys for AI services like OpenAI and Anthropic. Researchers also found that the malware could create long-term AWS access keys, modify IAM role trust policies, and add Azure federated identity credentials, potentially allowing attackers to maintain persistent access to victims' cloud resources even after the original GitHub tokens were revoked. There is currently no complete statistic confirming the success rate of these persistence operations.
Another security firm, StepSecurity, noted that attackers quickly reverted repository modifications and deleted workflow execution records after the GitHub Actions workflow started, with the entire cleanup process typically completing within one minute. This means enterprises may not detect traces of intrusion when reviewing code post-facto. Researchers advise companies using GitHub Actions to audit abnormal pull requests and workflow change histories since November 10. If malicious execution is confirmed, organizations must immediately rotate relevant tokens, cloud credentials, and API keys, and check cloud platforms for any anomalous permission additions or modifications.