Supply Chain Attacks on Repeat: Trivy, LiteLLM, and the Pattern Every Builder Should Know

Charm · April 8, 2026 · 2 min read · 5 sources

Analysis

Trivy Got Hit Twice in a Month: A Deep Technical Breakdown of Both Attacks

The most widely used open source vulnerability scanner was compromised twice in under 30 days, first via a stolen PAT from a misconfigured GitHub Actions workflow, then via credentials that survived incomplete rotation. If your security tooling itself is a supply chain target, the entire premise of 'scan to stay safe' needs rethinking.

The Axios Attack Exposes the External Blind Spot in Enterprise Security Tooling

Internal security tools can't see forgotten cloud deployments or unmonitored dev environments, which is exactly where supply chain attacks land. This piece makes a solid case for why external attack surface visibility needs to be a first-class capability, not an afterthought.

News

LiteLLM PyPI Supply Chain Attack: Malware in a 97M-Download AI Library Went Undetected

A poisoned LiteLLM version harvested SSH keys, cloud credentials, and Kubernetes configs, and zero security tools caught it. The only reason it was discovered was a bug in the malware itself that caused a crash.

Tools

How OS-Enforced Sandboxing Would Have Blocked the Axios RAT at Every Stage

This is a concrete technical walkthrough showing how capability-based sandboxing using Landlock and Seatbelt breaks the axios attack chain at network isolation, filesystem writes, and process execution. Worth reading if you're evaluating runtime controls for AI agents or CI environments.

Practical Commands to Detect and Remediate the Axios Supply Chain Compromise

A no-fluff remediation guide with actual terminal commands to scan lockfiles, check node_modules, and look for RAT artifacts across macOS, Windows, and Linux. Bookmark this and share it with your engineering team.

Stay Ahead

Delivered each morning.