LiteLLM hack chain follows exposed master key LiteLLM says that in the past weeks a supply chain compromise began with a master key that was committed to a public GitHub repo on May 27 and removed without reversal. On October 10, the actor used this key to access the LiteLLM agent platform, steal a GitHub CLI OAuth token, and gain access to the owner-level repository, as detailed in the post-mortem. The tainted 1.107.0 release was live on PyPI for less than two hours and attracted about 49,000 downloads. The incident shows how a single unrotated secret can bridge public code exposure to trusted CI paths and connected reinforcing identities. With post-2FA GitHub CLI tokens and internal workflow access, the attacker could move laterally, harvest cloud and model provider credentials, and make malicious changes that appeared to come from legitimate engineers. Open sources - closed narratives.

LiteLLM hack chain follows exposed master key LiteLLM says that in the past weeks a supply chain compromise began with a master key that was committed to a public GitHub repo on May 27 and removed without reversal. On October 10, the actor used this key to access the LiteLLM agent platform, steal a GitHub CLI OAuth token, and gain access to the owner-level repository, as detailed in the post-mortem. The tainted 1.107.0 release was live on PyPI for less than two hours and attracted about 49,000 downloads. The incident shows how a single unrotated secret can bridge public code exposure to trusted CI paths and connected reinforcing identities. With post-2FA GitHub CLI tokens and internal workflow access, the attacker could move laterally, harvest cloud and model provider credentials, and make malicious changes that appeared to come from legitimate engineers. Open sources - closed narratives.