On March 19, 2026, attackers calling themselves TeamPCP published a malicious version of the popular security scanner Trivy and rewrote almost every release tag of its GitHub Actions. The tampered code stole secrets from automated build pipelines, including cloud keys and SSH keys. The incident is tracked as CVE-2026-33634.
What is going on
Trivy is a free scanner that development teams run to look for known flaws in websites, servers and containers. Many teams start it automatically through GitHub Actions, which are small reusable building blocks for automated tasks.
The attackers published a malicious Trivy v0.69.4, then force-pushed 76 of the 77 trivy-action tags and all 7 setup-trivy tags so they pointed at malware. Malicious Docker Hub images v0.69.5 and v0.69.6 followed on March 22.
Think of a version tag as a label on a shelf. The label stayed the same, but someone swapped what was behind it. Teams that asked for a trusted version got malicious code that read the secrets stored in their pipeline.
Who is affected
Any team that ran trivy-action, setup-trivy or the affected Docker images during that week is affected. That includes agencies and freelancers who scan client websites or containers as part of their release process.
If you own a small business site, your own visitors were not targeted directly. The risk is that keys used to deploy or host your site were copied, which could let someone change the site later.
What to do now
- Ask your developer or agency whether Trivy ran in any build between March 19 and March 22, 2026.
- Upgrade
trivy-actionto 0.35.0 or later andsetup-trivyto 0.2.6 or later. - Rotate every secret the affected workflow could read: cloud access keys, SSH keys, deployment tokens and API keys.
- Pin GitHub Actions to a full commit SHA instead of a version tag, so a rewritten tag cannot change what runs.
- Review hosting and cloud account activity for logins or deployments you do not recognise.
How to check your own site
This attack happened inside build pipelines, so no website scan can detect it directly, but it is a good moment to confirm your live site is in order. The free Website Security Check looks for outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If deployment keys were exposed, you can also run a full scan on a site you have verified ownership of, which adds exposed-file and secret checks, port and service checks with CVE matching, and active OWASP Top 10 testing.
Source: GitHub Advisory GHSA-69fq-xp46-6x23, March 2026.
Comments
No comments yet.