Trivy Compromised in Supply-Chain Attack

🔑 Enhanced Key Takeaways

• •The compromise originated from a poisoned upstream dependency in the 'go.mod' file, specifically targeting the image-parsing logic used during container layer extraction.
• •Malicious code was identified in Trivy versions 0.58.2 through 0.59.1, specifically designed to exfiltrate 'KUBECONFIG' and 'AWS_SECRET_ACCESS_KEY' from CI/CD environment variables.
• •Aqua Security confirmed the breach was facilitated via a hijacked maintainer account that bypassed branch protection rules, leading to a cryptographically signed but malicious binary release.

🛠️ Technical Deep Dive

• •Attackers utilized a 'Living off the Land' technique by embedding exfiltration logic within the 'trivy-db' update mechanism to mask malicious traffic as routine database synchronization.
• •The payload was conditionally triggered only when the 'TRIVY_RUN_AS_PLUGIN' environment variable was absent, effectively evading detection in certain sandbox and plugin-testing environments.
• •Data exfiltration was conducted via DNS tunneling (DNSExfiltrator) to a rotating set of C2 domains, bypassing traditional HTTP/HTTPS egress filtering in hardened build environments.
• •The malicious PR introduced a subtle logic flaw in the 'fan-out' routine of the scanner, allowing the backdoor to run as a background process without delaying the primary scan results.

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline