Development pipelines and cloud environments were put at risk after an attacker used stolen GitHub access to probe more than 60,000 repositories. Roughly 4,800 compromised accounts submitted pull requests to test whether they could make changes. Researchers confirmed that secrets were stolen from at least 1,835 targets. The attacker used valid tokens rather than exploiting a weakness in GitHub Actions, then hid activity by reverting changes and deleting workflow records.

Why It Matters

The malware searched for repository secrets, cloud credentials, GitHub tokens and AI service keys. It could obtain cloud-session access in AWS, Azure and GCP, and attempt to establish persistence in AWS and Azure where permissions allowed. For leaders: developer and automation identities should be treated as privileged enterprise access. For defenders: review suspicious pull requests, workflow changes, installation hooks and unexplained gaps in run histories. The larger lesson is that trusted development access can become a bridge from source code to cloud control.

What Defenders Should Do

Revoke affected tokens, rotate every accessible secret and investigate unauthorized cloud changes.

Questions, corrections, or feedback about this story?Contact Daily Cyber News →

← Back to this Daily edition