Trivy compromised by TeamPCP: a security scanner becomes an attack vector on pipelines

2026-03-19 · Publisher : Aqua Security · Domain : Cloud & DevOps

On 19 March 2026, attackers publish a booby-trapped release of the Trivy scanner (v0.69.4) and hijack almost all tags of its GitHub Actions to steal CI/CD pipeline secrets. The group TeamPCP is blamed.

What changes

  • Trivy v0.69.4 booby-trapped and GitHub Actions tags hijacked on 19 March 2026.
  • Exposure window from 19 March 17:43 UTC to 20 March 05:40 UTC, according to Aqua Security.
  • A credential stealer targets CI/CD secrets, cloud keys, GitHub and Kubernetes tokens.
  • The stolen tokens then fuel the npm worm CanisterWorm.

### What changes On 19 March 2026, attackers use credentials compromised in an earlier incident to publish a malicious release of the Trivy vulnerability scanner (v0.69.4) and to rewrite the tags of the GitHub Actions trivy-action and setup-trivy. Aqua Security, which maintains the project, publishes a security advisory (GHSA-69fq-xp46-6x23, CVE-2026-33634). The group TeamPCP is blamed. ### Key facts - The exposure window runs from 19 March 17:43 UTC to 20 March 05:40 UTC: about 3 hours for the v0.69.4 binary, 12 hours for trivy-action and 4 hours for setup-trivy. - 76 of the 77 version tags of trivy-action and all 7 tags of setup-trivy are redirected to commits carrying a credential stealer, according to the advisory. - The malicious code collects environment variables, SSH keys, cloud credentials, Kubernetes tokens and GitHub tokens; Docker Hub images v0.69.5 and v0.69.6 were also published. - Root cause per Aqua: containment of the first incident had not been atomic, and refreshed tokens may have been observed by the attackers. - Safe versions: Trivy 0.69.3 or earlier, trivy-action 0.35.0, setup-trivy 0.2.6. Stolen tokens then fuelled an npm worm, CanisterWorm, from 20 March. ### Why it matters The trap is particularly cruel: a tool installed to secure pipelines becomes the entry point to their secrets. Teams that referenced trivy-action by a moving tag ran malicious code without changing their repository. The episode confirms the need to pin actions by SHA, enable immutable releases, limit the secrets reachable by jobs and assume exposure when in doubt. ### Takeaway Even a security tool can be the vector: pin actions by SHA, rotate secrets and audit runs from 19-20 March.

Links

Tags : Sécurité, CI/CD, Open Source, DevOps, Conteneurs