Futureweb

Security

LiteLLM says the October 21 release was pulled. Rotate credentials if you installed it.

LiteLLM says its October 21 pipeline was compromised and that the 1.107.0 artifacts were pulled the same day. Anyone who installed that release should rotate credentials.

The short version

LiteLLM says the October 21 release pipeline was compromised, that version 1.107.0 reached PyPI and container registries, and that those artifacts were pulled the same day. The project says the official source tag does not contain the added code, and that its private enterprise release was not affected. Anyone who installed the pulled artifacts should follow the project's notice and rotate credentials the host could reach.

The project's notice is the record

LiteLLM's October 21, 2026 notice, signed by its chief executive, its chief technology officer, its security director, and a lead engineer, says the release pipeline was compromised early that morning and that version 1.107.0 was pushed to PyPI and to container registries. The project says that version contained code that steals credentials and can load further code. It says all previous versions are safe, that the impacted releases have been pulled, and that the private enterprise release was not affected. Help Net Security's October 22 story is the wire account. An OpenSSF malicious-package report records the PyPI publication. This page does not reprint indicators from that report.the advisory is the story.

The windows are the project's clocks

LiteLLM says the PyPI release was public for about two hours, from 11:39 UTC to 13:23 UTC, and was then pulled. It says container tags, including a version tag and floating tags, pointed at a compromised image from 11:46 UTC until they were removed or pointed back at clean sources later that afternoon. The clocks matter because a host that never pulled in that window is not in the sentence. A host that pinned an older version is in the set the project calls safe. A host that took 1.107.0, even briefly, is in the set the project tells to rotate credentials.

The tag and the artifact are not the same object

The project says the official v1.107.0 source tag on GitHub does not contain the added code, and that the compromised artifacts were built from a repository the attacker controlled. A clean tag does not make a wheel that was live on PyPI clean. People who install from a tag they built themselves are in a different position from people who installed the published wheel or pulled the published image. The notice's point is that split. This page will not name the lookalike path, the added files, or a checksum.

What a person who installed it is told

LiteLLM tells anyone who installed or ran the affected artifacts to review its notice immediately, and to assume credential theft if that host could reach the network. The rotation list in the notice covers keys the host could see: cloud roles, provider keys stored for the proxy, database credentials, and other secrets in the environment. This brief will not copy the deletion steps or the file names. Those belong on the notice, where they can be corrected. The news sentence is narrower. The release was bad, it was pulled, and credentials on an affected host should be rotated from a clean machine.a signature on a package.

A second time is context, not a procedure

The OpenSSF report notes that an earlier LiteLLM publication, in March, was a previous case of the same kind. Help Net describes October 21 as another supply-chain publication. A pattern is relevant to whether a team pins versions. It is not a reason to print either payload. Teams that only run the private enterprise build are in the set the project excludes. Teams that float a latest container tag are in the set the clocks cover, even if they never typed the version number.

What this page will not print

It will not print domains, hashes, lock files, or commands. It will not print a decoder. Indicators in the OpenSSF report stay in that report. A reader who has to clean a machine should use LiteLLM's notice, which is being updated, rather than a newspaper paraphrase that can lag. A reader who only needs to know whether 1.107.0 is a version to refuse has the answer.

Who is in scope

Anyone who installed litellm 1.107.0 from PyPI, or who ran a LiteLLM container pulled during the window the project names. Enterprise customers on the private release are out of scope on the project's statement. People who never installed LiteLLM are out of scope. A proxy customer whose vendor pulled a bad image may be in scope through that vendor, which this page cannot see. Asked directly, Does this page print cleanup commands? No. The project published the steps. This page names the release, the window, and the credential advice.what a CVE identifier is.

What stays on the record

October 21, 2026 LiteLLM notice. Pipeline compromised. PyPI 1.107.0 live about two hours and pulled. Container tags affected the same day and then removed or repointed. Official source tag described as clean. Private enterprise release not affected. Previous versions described as safe. Credential rotation if the bad artifact was installed or run. Help Net retells the notice. OpenSSF records the package. No indicators and no cleanup commands on this page.what an advisory must name.

What would move the row

A LiteLLM update that changes the window, names a further version, or closes the investigation would be a later document. The notice itself says the investigation was still in progress on the evening of October 21. Until that update, the record is the notice plus two accounts that do not replace it. The short answer this page will stand on is this: LiteLLM says the October 21 release pipeline was compromised, that version 1.107.0 reached PyPI and container registries, and that those artifacts were pulled the same day. The project says the official source tag does not contain the added code, and that its private enterprise release was not affected. Anyone who installed the pulled artifacts should follow the project's notice and rotate credentials the host could reach.the key stays with the holder.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. LiteLLM
  2. Help Net Security
  3. OpenSSF

Questions

Does this page print cleanup commands?

No. The project published the steps. This page names the release, the window, and the credential advice.

Was the GitHub tag the bad copy?

LiteLLM says the official v1.107.0 source tag does not contain the added code. The compromised artifacts were built elsewhere and published over the release.

Who does the project say was not affected?

Enterprise customers on the private enterprise release. That sentence is the project's. It does not cover a public install of 1.107.0.

How long does LiteLLM say the package was public?

About two hours on PyPI, on the project's timeline, and a longer same-day window for container tags that were then removed or repointed.

What should someone who installed it do?

Treat the host as exposed, follow LiteLLM's notice rather than this page, and rotate credentials the host could reach. Previous versions are safe, the project says.