Mass GitHub account compromise used to seed credential-stealing code across 61,000+ repos
Researchers have identified a large-scale supply-chain campaign, tracked as 'wfx-loot', in which attackers leveraged 4,837 compromised GitHub accounts to interact with 61,764 repositories. The activity reportedly included probing repositories and opening pull requests that carried secrets-stealing malware, suggesting an automated or semi-automated effort to inject malicious code into legitimate codebases at scale.
GitHub and similar code-hosting platforms sit at the center of modern software supply chains, making them high-value targets for attackers seeking to harvest cloud credentials, API keys, and other secrets embedded in source code or CI/CD configurations. Compromising developer accounts—often through credential stuffing, phishing, or token theft—gives adversaries a trusted foothold to submit pull requests or commits that appear to come from legitimate contributors, increasing the odds that malicious changes slip past review. Once a stolen credential or secret is exfiltrated, attackers can pivot into cloud environments, exposing infrastructure, data, and downstream customers far beyond the original repository.
Campaigns of this nature are notable not just for their technical method but for their scale: thousands of compromised accounts touching tens of thousands of repositories indicates automation and a broad, opportunistic targeting strategy rather than a narrow, bespoke attack. This raises the risk that open-source maintainers and enterprise developers alike may unknowingly merge tainted contributions.
Organizations and individual developers should enable multi-factor authentication on all source-control accounts, routinely audit and rotate exposed secrets, and treat unsolicited or unfamiliar pull requests with heightened scrutiny. Repository owners should scan for hardcoded credentials, enforce signed commits where possible, and monitor for unusual account activity such as unexpected pull requests or access from unfamiliar locations. Cloud credentials discovered in code should be revoked immediately and never stored in plaintext within repositories.
Source: BleepingComputer
Read the original report ↗This is an original summary written by CyberSkii for reference. All rights to the underlying reporting remain with the publisher linked above.