Pattern: Supply Chain Attacks Now Route Through Security Scanners — The Tool That Audits Your Code Is the Attack Vector

Snyk / paddo.dev / Arctic Wolf·high signal

The TeamPCP campaign reveals a chilling pattern: the attackers first compromised Aqua Security's Trivy scanner (a security tool), then used that foothold to backdoor LiteLLM's CI/CD pipeline, then pivoted to Checkmarx KICS. The attack vector was a poisoned GitHub Action in a security scanner — meaning the tool developers trust to find vulnerabilities was the entry point. As paddo.dev noted: 'a security scanner was the entry point.' For builders using MCP servers, CI/CD tools, and coding agents that install dependencies, this pattern demands a rethink: your security tooling is itself an attack surface. Pin dependencies, verify checksums, and treat CI/CD Actions as code requiring review.