The European Commission has officially confirmed a significant data breach of its Amazon Web Services (AWS) environment, with threat actors stealing more than 300 gigabytes of data — including personal information. The breach has been linked to the compromised Trivy open-source container security scanner, which attackers turned into a supply chain attack vector earlier this year.
What Was Stolen
According to SecurityWeek's reporting, the stolen data includes personal information of European Commission staff and stakeholders hosted in the compromised AWS environment. The Commission operates a substantial cloud infrastructure on AWS for internal workloads, and the breadth of data accessed spans multiple departments and entities within the EU's executive body.
Investigators are still working to determine the full scope of what data was exfiltrated from the 300GB cache.
Connection to the Trivy Supply Chain Attack
The breach traces back to the Trivy supply chain attack disclosed in late March 2026. Trivy, a widely used open-source vulnerability scanner for containers and cloud infrastructure, had 75 of its GitHub release tags hijacked by attackers. Malicious versions of the tool were distributed through GitHub Actions workflows, enabling attackers to steal CI/CD secrets, credentials, and environment variables from organizations running the compromised scanner in their pipelines.
The European Commission's cloud infrastructure relied on Trivy as part of its container security scanning workflow. When compromised versions of Trivy ran in the Commission's CI/CD environment, attackers were able to harvest AWS credentials — ultimately enabling direct access to the S3 environment and broader AWS account.
ENISA Attribution: TeamPCP
The EU's cybersecurity agency, ENISA, has separately attributed the attack to the TeamPCP hacking group — the same group responsible for the Telnyx PyPI supply chain attack that dropped info-stealer malware hidden in WAV audio files. TeamPCP has been escalating its activity, with the European Commission breach representing its highest-profile target to date.
ENISA's investigation found that the Commission was one of at least 30 EU entities impacted by the TeamPCP campaign, which weaponized compromised open-source tooling to gain initial access to cloud environments across EU institutions.
Commission Response
The European Commission has:
- Taken affected AWS infrastructure offline for forensic investigation
- Notified relevant EU data protection authorities under GDPR obligations
- Engaged ENISA and member state Computer Security Incident Response Teams (CSIRTs) to assist with the investigation
- Begun rotating all credentials and access keys across affected systems
The Commission stated it is working to "identify and inform all individuals whose personal data may have been affected."
Broader Implications
This breach highlights the systemic risk posed by supply chain attacks on security tooling itself. Organizations that use open-source security scanners, package managers, and CI/CD tools as trusted infrastructure components face a compounding risk: the tools meant to find vulnerabilities can themselves become the attack vector.
Key lessons from this incident:
- Verify integrity of security tooling — use cryptographic signatures and checksums when pulling security scanners into pipelines
- Pin tool versions explicitly — avoid pulling "latest" tags from GitHub releases without integrity verification
- Least-privilege cloud credentials — CI/CD systems should have tightly scoped IAM permissions; scanner tools should never have broad S3 or account-level access
- Monitor for unusual cloud activity — large S3 data transfers during or after CI/CD pipeline runs should trigger immediate investigation
The Trivy attack underscores that threat actors increasingly understand that the security toolchain is a high-value, low-scrutiny target. If they can compromise what defenders trust, they can operate invisibly inside hardened environments.
Sources: SecurityWeek, The Record