Trivy Poisoned in EU Commission Breach

🔑 Enhanced Key Takeaways

• •The breach originated from a February compromise of Trivy's GitHub Actions environment (CVE-2026-33634), where TeamPCP exploited incomplete credential rotation to force-push malicious code to 76 of 77 version tags.
• •The stolen data, totaling 340 GB uncompressed (91.7 GB compressed), impacted up to 71 clients of the Europa web hosting service, including 42 internal European Commission clients and at least 29 other Union entities.
• •TeamPCP utilized the stolen AWS API key to deploy TruffleHog within the Commission's environment to discover additional secrets, and attempted to evade detection by creating and attaching new access keys to existing user accounts.

🛠️ Technical Deep Dive

• •Initial Access: Exploitation of CVE-2026-33634 in Trivy's GitHub Actions environment allowed TeamPCP to gain a privileged access token.
• •Supply Chain Poisoning: Attackers manipulated trusted Trivy version tags to force CI/CD pipelines to pull down credential-stealing malware.
• •Credential Harvesting: The malware was designed to exfiltrate AWS, GCP, and Azure cloud credentials, Kubernetes tokens, Docker registry credentials, database passwords, TLS private keys, SSH keys, and cryptocurrency wallet files.
• •Persistence and Evasion: Attackers created and attached new access keys to existing user accounts to maintain access and evade detection.
• •Discovery Tooling: TeamPCP utilized the open-source tool TruffleHog to scan for and validate additional AWS credentials via the Security Token Service (STS).

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline