According to the project's findings, a configuration file was committed on May 27, 2026 to the public LiteLLM-Labs/lite-harness repository, and that file inadvertently contained the master key for a deployment of the Agent Platform. The exposure of this credential gave the attacker a path into the release pipeline, allowing them to push a compromised package version.

The incident highlights the outsized risk posed by secrets leaking into public code repositories. A single committed configuration file was enough to compromise the project's release process and, by extension, anyone who installed the affected package version.

Key facts as disclosed:

• The exposed credential was a master key for a deployment of the LiteLLM Agent Platform.
• The key was published in a configuration file committed to the public LiteLLM-Labs/lite-harness repository on May 27, 2026.
• The attacker used the access to push a malicious version of the LiteLLM Python package.
• The disclosure was made by LiteLLM on Friday.

Users of the package should review their dependency versions and treat any install pulled during the exposure window with suspicion, particularly in environments where the package handles credentials or has access to CI/CD systems.

Source: The Hacker News

Has your organization pinned LiteLLM to a known-good version, or are you still tracking which release was affected?