BerriAI: stolen GitHub tokens apparently used to publish compromised LiteLLM 1.107.0
BerriAI says it has found a possible way one of the stolen GitHub tokens leaked and has paused LiteLLM releases. It has not yet found how the attacker reached the other engineers' accounts, and says a third account was used to delete workflow records.
By Emerson Redding · Published · Updated
Why it matters
Organizations that ran LiteLLM 1.107.0 may be at risk. BerriAI says it has identified a potential vector for one leaked token but not how the attacker reached the other engineers' accounts. It says it has seen no ongoing suspicious activity, and that customers on its private enterprise release were not impacted.
BerriAI said an attacker used three engineers' GitHub accounts, apparently through stolen GitHub CLI OAuth tokens, during the process that produced LiteLLM version 1.107.0. The company said one account started the release run and another approved it, according to its update on GitHub issue #47826.
Update, 1:35 p.m. CT: BerriAI says it has found a possible way one of the tokens leaked and has paused LiteLLM releases; its incident report says a third engineer's account was used to delete workflow records after the release.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.