When Your Security Scanner Becomes the Weapon: Lessons from the Trivy Supply Chain Attack

This article was originally published on LucidShark Blog. When Your Security Scanner Becomes the Weapon: Lessons from the Trivy Supply Chain Attack On March 19, 2026, a group called TeamPCP compromised 75 tags of the aquasecurity/trivy-action GitHub Action. The attack involved silently executed attacker-controlled code that appeared to function normally while exfiltrating credentials. The incident lasted five days before detection on March 24. Critical Warning: If your CI/CD pipeline ran trivy-action or setup-trivy without a pinned commit SHA between March 19 and March 24, 2026, treat all secrets accessible from that pipeline as compromised. How the Attack Worked TeamPCP exploited GitHub Actions mutable tag system by compromising a maintainer account at Aqua Security through targeted phishing. They force-pushed release tags to point to commits containing WAVESHAPER.V2, a cross-platform remote access tool. The attack remained nearly undetectable because: The action executed successfully