Attacker hijacks thousands of GitHub accounts to deploy CI secret stealer across repositories

Executive Briefing
“An attacker used stolen credentials from thousands of GitHub accounts to plant...”
Key Takeaways
- 1.The attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in over 1,806 repositories.
- 2.The stealer is built to gather authentication tokens, AWS, Azure, and GCP cloud service keys, and sensitive configuration files from runners.
- 3.Researchers noted that attacks began with pull requests titled dependency audit notes originating from wfx-docs branches.
An attacker used stolen credentials from thousands of GitHub accounts to plant secret-stealing malicious code into continuous integration workflows. The malware harvests cloud keys, service credentials, and environment variables from runner environments.
Key Developments and Technical Context
The attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in over 1,806 repositories.
The stealer is built to gather authentication tokens, AWS, Azure, and GCP cloud service keys, and sensitive configuration files from runners.
Researchers noted that attacks began with pull requests titled dependency audit notes originating from wfx-docs branches.
Strategic Analysis and Industry Implications
The automation of injecting malicious code into CI workflows highlights the severe risk facing modern software supply chain security.
The malware's ability to manipulate cloud trust policies indicates persistent access risks even after administrators rotate credentials.
Outlook and Key Factors to Watch
It remains unclear exactly how the attacker initially acquired the thousands of GitHub account credentials.
It is not yet determined whether the group behind the November campaign shares identity with the October GhostAction wave.







