GhostAction GitHub Supply Chain Attack Exposes 3,325 Secrets

The GhostAction GitHub supply chain attack has drawn global attention. Researchers revealed that hackers exploited GitHub Actions workflows to steal 3,325 secrets from 817 repositories. The campaign affected 327 developers and compromised critical tokens, highlighting the risks of insecure CI/CD pipelines.

How the Attack Worked

The attack surfaced in early September 2025 when investigators discovered malicious commits in the FastUUID project. The code was pushed through a compromised maintainer account named Grommash9.

The altered GitHub Actions workflow automatically ran during push events and manual triggers. Once active, it collected environment secrets and exfiltrated them using a curl POST request to attacker-controlled servers. This method allowed silent theft without raising immediate alarms.

Scale of the Breach

The campaign was not limited to one repository. Researchers confirmed that 817 repositories were compromised, leaking 3,325 secrets in total. These included:

• GitHub personal access tokens
• PyPI and npm tokens
• DockerHub credentials
• AWS keys and Cloudflare API tokens

The stolen credentials represent serious supply chain risks since attackers could use them to access cloud services, publish malicious packages, or escalate intrusions.

Response to the Incident

GitGuardian disclosed the campaign on September 5, 2025. The firm filed GitHub issues in 573 repositories to warn maintainers. At the same time, security teams at GitHub, npm, and PyPI were notified.

Roughly 100 repositories had already reverted the malicious commits before disclosure. Still, the scale of stolen secrets shows how damaging automated workflow exploitation can be when left unchecked.

Why It Matters

The GhostAction GitHub supply chain attack shows how insecure CI/CD automation creates weak points. Developers trust these pipelines, but attackers exploit them to steal critical credentials.

Conclusion

The GhostAction GitHub supply chain attack compromised 3,325 secrets across hundreds of repositories. While many repos reverted changes and vendors were alerted, the incident emphasizes that CI/CD workflows must be secured with the same rigor as production systems. Without stronger defenses, attackers will continue to exploit automation to infiltrate software supply chains.