LiteLLM reveals breach cause: coding agent got org owner's GitHub token

LiteLLM published the root cause of its October 21 supply chain breach: its cloud coding agent was given an organization owner's personal GitHub token just to open pull requests. A master key left live for 136 days let an attacker obtain the token, exfiltrate repository secrets within 44 minutes and publish a poisoned PyPI release 11 days later.

• The agent used an org owner's personal token instead of a repo-scoped GitHub App token
• The platform master key stayed valid for 136 days after the file was scrubbed from git history
• Within 44 minutes the attacker dumped repo secrets via two throwaway ci-tmp branches
• Stolen tokens were used 11 days later to publish a malicious LiteLLM release to PyPI