A threat actor known as TeamPCP compromised Aqua Security’s widely used open-source scanner Trivy on 19 March 2026, turning a security tool embedded in thousands of CI/CD pipelines into a credential stealer. The incident is tracked as CVE-2026-33634 and rated critical.
What happened
Using credentials retained after an incompletely contained earlier incident, the attackers pushed a malicious v0.69.4 tag that triggered official release builds, poisoning GitHub release binaries and container images on Docker Hub, GHCR and ECR. Wiz reports that 75 of 76 tags in aquasecurity/trivy-action and all 7 tags in aquasecurity/setup-trivy were force-pushed to malicious commits, and imposter commits spoofing other developers were placed in actions/checkout and aquasecurity/trivy. Malicious images 0.69.5 and 0.69.6 followed on 22 March. The campaign then spread: a self-propagating npm worm dubbed CanisterWorm used stolen publish tokens, Checkmarx’s KICS and ast-github-action GitHub Actions were compromised with the same stealer, and a tampered LiteLLM package on PyPI was also attributed to TeamPCP. Depending on the component, exposure windows ranged from about 3 to 12 hours.
Technical details
In GitHub Actions the payload scraped secrets directly from Runner.Worker process memory, bypassing log masking, and swept more than 50 filesystem paths for SSH keys, cloud credentials, Kubernetes tokens and crypto wallets. Data was encrypted, packed as tpcp.tar.gz and sent out; as a fallback, the malware created a tpcp-docs repository in the victim’s GitHub account. On developer machines the binary installed a sysmon.py systemd user service that polled an ICP-hosted URL for further payloads.
IOCs published by Wiz include scan.aquasecurtiy[.]org, plug-tab-protective-relay.trycloudflare.com, tdtqy-oyaaa-aaaae-af2dq-cai.raw.icp0.io and IP 45.148.10.212.
Who is affected
Any pipeline that referenced Trivy actions by tag or pulled Trivy 0.69.4–0.69.6 during the exposure window. CERT-EU later assessed that a European Commission AWS breach began with secrets stolen this way.
Recommendations
- Search runner logs from 19–23 March for
tpcp.tar.gz,aquasecurtiyandcheckmarx.zone, and your GitHub organisation fortpcp-docsrepositories. - Remove Trivy 0.69.4–0.69.6 artefacts and follow Aqua’s advisory for clean versions.
- Rotate every secret available to affected workflows: cloud keys, registry and package-publishing tokens, SSH keys.
- Pin all GitHub Actions to full commit SHAs rather than mutable tags.
- Leaked developer and cloud credentials can also be checked against stealer-log data such as TAYNOPIS to confirm rotation is complete.