SignalMacro
LiteLLM supply chain attack started with an exposed master key
Supply chain attack began with exposed master key, signaling systemic security risk.
Context
What happened: LiteLLM traced a supply chain attack to a master key accidentally committed to a public GitHub repository in May. A poisoned version 1.107.0 of its open source AI gateway was uploaded to PyPI and container registries.
Key numbers: The trojanized package was on PyPI for less than two hours and received
Why it matters: The key gave the attacker owner-level access to all LiteLLM GitHub repositories, and the stolen GitHub CLI tokens were post-2fa, so they did not trigger sudo mode authentication. LiteLLM is revoking every token tied to internal systems and vendor platforms.
What changed
LiteLLM traced a supply chain attack to a master key accidentally committed to a public GitHub repository in May. A poisoned version 1.107.0 of its open source AI gateway was uploaded to PyPI and container registries.
Why it matters
The key gave the attacker owner-level access to all LiteLLM GitHub repositories, and the stolen GitHub CLI tokens were post-2fa, so they did not trigger sudo mode authentication. LiteLLM is revoking every token tied to internal systems and vendor platforms.