April 9, 2026
CI/See‑Ya Keys
How the Trivy supply chain attack harvested credentials from secrets managers
Stolen keys, finger‑pointing, and a “this is an ad” pile‑on
TLDR: Attackers hid code in Trivy’s official release to copy API keys from build systems, and millions of automated jobs ran it. Comments split between “we already knew secrets in builds are risky,” accusations of a product pitch, and calls to pin versions and use short‑lived tokens to avoid repeat chaos
The internet is losing it over the Trivy mess — attackers slipped credential‑stealing code into the popular security scanner, and automated build systems (think robot scripts that ship your app) happily ran it. Because most “secret keepers” put your key back into the system as a plain text value, the malware just grabbed it. Scans looked clean. Keys walked out the door. Cue maximum drama.
Right away, the author behind VaultProof jumped in: “keys in plain text are the real villain,” pitching its split‑key approach where no full key ever exists in the build. Some applauded the clarity, others rolled their eyes — “ad, thinly veiled as an article,” snapped one commenter, adding that rival tools like OneCli already do this. The “we told you so” crowd piled on too: veterans claimed everyone knew that secrets sitting in the build environment were an accident waiting to happen, and bragged they already fork every third‑party GitHub Action. Meanwhile, pragmatists offered fixes: dump common secret interfaces, use short‑lived tokens fetched just‑in‑time (no permanent keys!), and pin versions to unchangeable hashes instead of “tags” that can be swapped under your feet.
Memes flew: “CI/See‑Ya Keys,” “Trust Me Bro v0.69.4,” and screenshots of environment variables with dramatic red circles. Under the jokes, the vibe is clear: the attack worked because the keys were there to steal, and the community is torn between buy a new tool, do better hygiene, or both. Either way, nobody’s trusting their robots without receipts anymore.
Key Points
- •On March 19, 2026, attackers injected credential-harvesting code into Aqua Security’s Trivy v0.69.4 release binary.
- •The attack used mutable Git tags and a self-declared commit identity to compromise the official release.
- •Compromised trivy-action and setup-trivy GitHub Actions propagated the payload to millions of CI/CD pipelines.
- •The malware read plaintext API keys from environment variables set by secrets managers at runtime and exfiltrated them.
- •The article proposes VaultProof’s split-key architecture so full API keys never exist in the CI/CD environment, preventing harvest.