An unrevoked master key exposed in a public repository allowed attackers to infiltrate the LiteLLM release pipeline, resulting in the malicious v1.107.0 release deployed to PyPI and container registries.

How the breach started

The problem began on May 27, 2026, when a key configuration was accidentally published to the LiteLLM open source repository. Although the developers quickly caught the error and patched it, they forgot to revoke the key.

On October 10, 2026, an unknown attacker used the inactive but non-cancelled key to log into the platform. From there, he was able to extract a digital access key associated with an administrator account.

Between October 10 and 12, the attacker created temporary, short-lived branches of code to run internal processes and gather additional keys and digital assets.

READ ALSO

Dutch security firm hacked millions of foreign computers to stop hidden threat

The publication of the infected version

On October 21, 2026, the perpetrator changed the release process to…