Mastodawn

A supply chain attack hit LiteLLM on March 24th.

Two PyPI versions. Six hours. Your AWS keys, SSH keys,
DB passwords, Kubernetes tokens — silently exfiltrated.
You didn't even have to install it directly.
A transitive dependency was enough.

EVERYTHING FROM A TRANSITIVE DEPENDENCY!

Show thread

devsimsek 2d ago

The attacker compromised Trivy — LiteLLM's own
CI/CD security scanner — and used it to push
malicious packages to PyPI under a maintainer's account.
v1.82.8 even dropped a persistence file into
site-packages that survives uninstall.
The security tool. Was the attack vector.

Show thread

devsimsek

Hot take: this isn't an "AI" problem.
ML and deep learning are math. Gradient descent
doesn't steal your secrets.
What steals your secrets is a rushed,
overhyped ecosystem where devs blindly
`pip install` without reading a changelog.
I review every dependency update before I trust it.
It's boring. It works.

Show thread

devsimsek 2d ago

I wrote up the full breakdown — what happened,
what was stolen, the uncomfortable pattern behind
incidents like this, and what to do if you're affected.
👉 https://smsk.dev/2026/03/26/the-litellm-breach-why-i-dont-integrate-ai-into-my-apps-and-you-might-want-to-reconsider-too/
If your stack depends on LLM middleware,
this one's worth a read. 🔒

The LiteLLM Breach: Why I Don't Integrate AI Into My Apps (And You Might Want to Reconsider Too) - devsimsek's Blog

LiteLLM's supply chain breach in March 2026 compromised credentials via malicious PyPI packages. Here's what happened and why AI middleware deserves more scrutiny.

devsimsek's Blog