LiteLLM Got Hacked. Your AI Agent Had No Runtime Security.

title: "LiteLLM Got Hacked. Your AI Agent Had No Runtime Security." published: false description: "A supply chain attack hit one of the most popular LLM proxy libraries. Here's why every AI agent needs a runtime security layer — and how to add one in 2 lines of Python." tags: ai, python, security, opensource cover_image: (terminal screenshot showing blocked injection attempt) LiteLLM was hit by a supply chain attack in March 2026. If you were running an AI agent that depended on it — and thousands of projects do — your entire stack was exposed. Every prompt, every API key, every tool call routed through the compromised dependency. This wasn't a theoretical attack. It was trending on Hacker News with 395 points. And the uncomfortable truth is: most AI agent codebases had zero defense against it. No input validation on LLM responses. No output scanning. No audit trail. No way to even detect that something was wrong until after the damage was done. The real problem isn't LiteLLM. It's the