Update: This follows my post LiteLLM 1.107.0 Was Trojaned.
The Register reports LiteLLM traced the attack to a master key committed to a public GitHub repo on May 27. They removed the commit but never revoked the key. On October 10 the attacker used it to get into LiteLLM’s agent platform, grabbed a GitHub CLI OAuth token with owner access to every repo, then stole more tokens from two maintainers. The poisoned 1.107.0 was on PyPI for under two hours and got about 49,000 downloads, per Wiz.
The infostealer went after browser credentials and cookies, cloud keys, and API keys for OpenAI, Anthropic, Cohere and others.
Checklist
- If 1.107.0 ever ran anywhere, assume every reachable credential is burned and rotate it.
- Deleting a leaked secret from git isn’t enough. Revoke it.
- Scan your repos for committed secrets.
God Bless, and Needs Garlic!
