LiteLLM supply chain attack started with an exposed master key
LiteLLM supply chain attack began with an exposed master key on GitHub.
Run LiteLLM?
Get an email when a reviewed story names LiteLLM, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
Summary
LiteLLM experienced a supply chain attack where a master key was accidentally committed to a public GitHub repository. This key allowed an attacker to gain owner-level access to LiteLLM's GitHub repositories, enabling them to inject malicious code into the LiteLLM package distributed via PyPI. The compromised package, version 1.107.0, contained an infostealer and a remote access trojan, leading to the potential exfiltration of sensitive credentials and API keys.
The lesson from this incident
Full lessonA developer accidentally committed a master key to a public GitHub repository, granting an attacker owner-level access to LiteLLM's entire GitHub organization. With that access, the attacker injected an infostealer and remote access trojan into version 1.107.0 of the LiteLLM PyPI package, potentially compromising credentials and API keys of every downstream user who installed it. This incident illustrates how a single secret exposure can cascade into a full supply chain compromise affecting thousands of consumers. Secrets in source code are a well-documented, preventable risk that automated scanning tools can catch before they ever reach a public repository.
What helps against this
How we list vendors- Secrets management
API keys, tokens and passwords stop leaking from code, chat and configuration files.
- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Software supply chain security
Malicious and vulnerable open-source packages are caught before they ship.
Indicators of Compromise
- malware — infostealer
- malware — remote access trojan