LiteLLM supply chain attack started with an exposed master key
A trojanized version of LiteLLM (1.107.0) containing an infostealer and remote access trojan was uploaded to PyPI and container registries, receiving approximately 49,000 downloads before removal. The attack originated from a master key left exposed in a public GitHub repository since May 27. An attacker used the key to gain access to LiteLLM's platform, extracted a GitHub CLI OAuth token, and obtained owner-level access to all repositories. The company failed to revoke the master key after discovering the exposure.
Key points
- Poisoned LiteLLM package deployed via PyPI received 49,000 downloads in under two hours
- Root cause: exposed master key in public GitHub repository from May 27
- Attacker gained owner-level access to all LiteLLM repositories through GitHub OAuth token theft
Summary and key points written by AI from the headline and a short excerpt, so they can be incomplete or wrong. The Register did the reporting; read the original for the full story.
Read the full story at The Register
