CERT-EU: Trivy supply-chain attack led to European Commission AWS breach

CERT-EU says an AWS key stolen via the poisoned Trivy scanner let TeamPCP breach the Commission's Europa hosting, hitting 42 internal and 29+ EU clients.

TechLogHub Engineering Team
April 3, 2026
3 min read
0 views

Share Article

CERT‑EU: European Commission hack exposes data of 30 EU entities

CERT-EU has published its account of the March 2026 breach of the European Commission's Europa.eu web hosting platform, and the entry point is one many engineering teams share: a compromised release of Trivy, the open-source vulnerability scanner that runs in countless CI pipelines. A single AWS API key taken from that environment was enough to reach the Commission's AWS account. If your pipelines run third-party actions with cloud credentials in scope, this is your threat model too.

What happened

On 19 March 2026, attackers compromised Aqua Security's Trivy distribution. Aqua says Trivy binary v0.69.4, nearly all tags of the aquasecurity/trivy-action GitHub Action and several tags of aquasecurity/setup-trivy were pointed at malicious code for several hours, and that Docker Hub images tagged 0.69.5 and 0.69.6 were also affected on 22 March. The payload ran before the real scan, collected environment variables, cloud credentials, SSH keys, Kubernetes tokens and other secrets, and sent them to a typosquatted domain. Aqua attributes the compromise to a group tracked as TeamPCP.

According to CERT-EU, the Commission received a compromised Trivy version through normal update channels. On 19 March the attacker obtained an AWS API key, immediately ran TruffleHog to look for more secrets and validated credentials with STS calls. The key carried management rights that could have allowed movement into other Commission AWS accounts, though CERT-EU found no evidence of that. To persist quietly, the attacker created and attached a new access key to an existing IAM user.

On 24 March the Commission's security operations centre received alerts about possible misuse of Amazon APIs, possible account compromise and abnormal network traffic. CERT-EU was notified on 25 March, the compromised secret was secured and the new keys were disabled. The Commission disclosed the incident on 27 March. On 28 March, the ShinyHunters extortion group published the stolen dataset on its leak site. CERT-EU published its findings on 2 April.

Who is affected

  • Clients of the Europa web hosting service: up to 71, made up of 42 internal Commission clients and at least 29 other EU bodies.
  • The leaked data: 91.7 GB compressed (about 340 GB uncompressed), including names, usernames and email addresses, and at least 51,992 outbound email files (2.22 GB). Most are automated notifications, but bounce-backs may contain user-submitted content. Database analysis was still ongoing.
  • Any organisation that ran affected Trivy versions or actions between 19 and 20 March 2026, or pulled the bad Docker images on 22 March.

No Europa websites were taken offline or altered.

What it means for developers and engineering teams

Security scanners are trusted, privileged code. They run in CI with access to the same secrets the build has, and teams often reference them by mutable tags like @v0.x or @master. When the attacker force-pushed those tags, every pipeline that resolved them pulled the malicious version on its next run.

  • Tags are not versions. A Git tag can be moved; a commit SHA cannot. Aqua notes that GitHub's "Immutable" release badge did not prevent tag force-pushes here.
  • Long-lived cloud keys in CI are the prize. A static AWS key with management rights turned a CI compromise into a cloud-account compromise. OIDC federation with short-lived, narrowly scoped role credentials would have limited both lifetime and reach.
  • Detection worked, but days later. CloudTrail-based alerts on API misuse and traffic spikes caught it in five days. Specific detections on CreateAccessKey for existing users and on bursts of GetCallerIdentity calls would shorten that.

What to do now

  1. Check for affected versions: Trivy v0.69.4, Docker images 0.69.5 and 0.69.6, and workflows using trivy-action or setup-trivy during 19 to 20 March 2026. Safe versions per Aqua are Trivy v0.69.2 to v0.69.3, trivy-action v0.35.0 and setup-trivy v0.2.6.
  2. Rotate every secret exposed to affected runs: cloud keys, GitHub tokens, registry, SSH, Kubernetes and package-publish credentials.
  3. Search your GitHub organisations for unexpected repositories named tpcp-docs, which the malware used as an exfiltration fallback.
  4. Pin actions to full commit SHAs:
    uses: aquasecurity/trivy-action@<40-char-commit-sha> # v0.35.0
  5. Replace static CI keys with OIDC roles scoped to the minimum actions each job needs.
  6. Hunt in CloudTrail for new keys on existing users:
    aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=CreateAccessKey --max-results 50

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.