Trivy supply chain attack breaches EU Commission data

🔑 Enhanced Key Takeaways

• •The breach was facilitated by TeamPCP force-pushing malicious commits to 76 of 77 version tags in the 'trivy-action' repository and all 7 tags in 'setup-trivy', causing automated CI/CD pipelines to pull poisoned code without changing version numbers.
• •The attack originated from residual access TeamPCP retained following an incomplete credential rotation after a separate, earlier security incident in late February 2026.
• •The stolen data was exfiltrated as an encrypted 'tpcp.tar.gz' archive and subsequently leaked on the dark web by the ShinyHunters extortion group on March 28, 2026.

🛠️ Technical Deep Dive

• •Initial Access: Exploitation of residual credentials from a prior incident to compromise the 'aqua-bot' service account.
• •Payload Execution: Malicious code injected into 'entrypoint.sh' executed before the legitimate Trivy scan, masking the activity from pipeline operators.
• •Credential Harvesting: The malware used tools like TruffleHog to scan for AWS IAM keys, GCP service account keys, and Kubernetes secrets.
• •Exfiltration Mechanism: Stolen data was encrypted using a hybrid AES-256-CBC + RSA scheme and exfiltrated via HTTP POST to attacker-controlled domains (e.g., scan.aquasecurtiy[.]org).
• •Persistence: Attackers created and attached new AWS access keys to existing user accounts to maintain access and evade detection.

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline