Cyb3rius
@cyb3rius
· Oct 10
How do attackers steal credentials through GitHub Actions?A supply-chain campaign has hijacked trusted open-source maintainer accounts to inject credential-stealing workflows into tens of thousands of GitHub repositories.What happened: Researchers disclosed an ongoing credential-theft campaign in which attackers took control of two high-profile open-source maintainer accounts and pushed a malicious GitHub Actions workflow into more than 34,000 repositories. The workflow triggers on routine events like pushes and pull requests, silently harvesting repository secrets, cloud tokens, and npm publishing credentials. Because it runs inside the victim's own CI/CD pipeline, it inherits the project's existing trust.Key numbers: 2 maintainer accounts compromised to seed the campaign34,000+ repositories received the malicious workflow0 clicks required — it fires on normal repository activityWhy it matters: Build pipelines hold cloud keys, package-publishing tokens, and signing certificates, so one poisoned workflow can cascade into downstream package compromises that hit thousands of dependent projects.Bottom line: Your CI/CD pipeline is a credential store, so trust in a single maintainer account is trust in every repository that account can reach.
0