THREAT BRIEFING · 16.11.2026 DEENFRES

News

LiteLLM Update Steals Credentials From AI Environments

By Benedikt Langer · November 4, 2026 · 5 min read

On 21 October the AI software LiteLLM shipped a compromised version containing malware designed to steal credentials. The vendor advises anyone who installed it to replace every credential that was reachable from the infected system.

Key takeaways

  • The compromised version 1.107.0 contained a credential stealer. Tools for remote code execution came with it, delivered via PyPI and Docker.
  • The malware starts up with Python itself. According to JFrog’s analysis it runs even when an application never loads LiteLLM.
  • Affected users should replace every credential that was reachable. The vendor also recommends rebuilding affected environments.

Related: AOMEI updates: minutes were enough for a backdoor  ·  When purchased AI routers smuggle in malicious code

The time window on 21 October

On the morning of 21 October (UTC) the Python package repository PyPI listed a new version of the AI software LiteLLM. PyPI is the central source from which developers download ready-made building blocks for the Python programming language. Just under two hours later, all seven prebuilt installation packages of version 1.107.0 were available there with malware included. In technical jargon these packages are called wheels.

The project also shipped the compromised version via Docker. Docker packages software together with its environment in so-called containers that start on servers without any additional setup. According to the vendor, version 1.107.0 contained a program for stealing credentials. On top of that came tools that let attackers remotely execute code on an infected system.

What is an infostealer? An infostealer is malware that specifically searches an infected computer for stored credentials. Depending on its design, this includes passwords, keys for cloud services and login data from programs. The loot goes to the attackers, who can use it to gain access to further systems.

Danger beyond LiteLLM

The significance of the incident lies in its startup mechanism. According to the analysis by JFrog Security Research, the malicious code in version 1.107.0 executes when Python starts, through so-called startup hooks. These are routines that Python automatically runs on every program launch. The malware therefore runs even when an application never loads LiteLLM.

According to the malware analysis by Datadog Security Labs, the stealer targets logins for cloud services, developer keys and credentials for AI services. Passwords saved in browsers and the credentials from the LiteLLM database are also in its sights. For affected companies the risk therefore extends beyond actual LiteLLM usage. Other corporate accounts that are reachable from the infected system are at risk too.

Another detail concerns the review of program code. According to JFrog’s comparison, the published source code archive of the version does not contain the malicious files from the prebuilt installation packages.

Recommendations for affected companies

The vendor’s recommendation is far-reaching. Affected users should replace every credential that was reachable from the infected system. In IT this process is called rotation: old keys and passwords become invalid and new ones take their place. Keys for AI providers and database passwords are explicitly named. The scope therefore depends on which accounts and systems were reachable from the affected system.

Rebuilding affected environments comes on top. The vendor warns against the package manager pip, the standard tool for installing Python packages: according to the vendor, cleanup should not begin with it.

For the period after removing the malware, the advice from Datadog Security Labs is to return to version 1.106.2. This version should be pinned explicitly. Experts call this pinning: the configuration names an exact version number so that no automatic update pulls in a newer release. Affected users should also check their logs to see whether the exposed credentials were used.

How the attackers got hold of the credentials

On 23 October LiteLLM disclosed the cause. On 27 May an administration key for an internal platform had accidentally ended up in a public repository. The file was deleted after roughly three hours, but the key was never revoked. On 10 October the attackers used it to grab the GitHub token of an organization owner and then the tokens of two more maintainers. With these access rights they modified the release workflow and approved the compromised release. JFrog’s investigation did not establish a connection to the attacker group TeamPCP. The same applies to a link with an access route used earlier.

On the evening of 21 October, at 20:30 UTC, the incident was considered contained. For operators this creates a review task on their own side: credentials that were public at any point count as compromised and should be revoked, even if the file was deleted long ago.

Frequently Asked Questions

Each question is locked. Tap to unlock the answer.

Are customers of the LiteLLM Enterprise edition affected?

According to the vendor, enterprise customers with the private Enterprise edition were not affected by the attack. The compromised version 1.107.0 circulated via PyPI and Docker.

Does the malware also run on Windows?

Partially. According to JFrog’s analysis, the backdoor for fetching additional code does not work fully on Windows. The credential stealer still runs there.

Did the attackers load additional malicious code?

Outside its own investigation, Datadog has not observed a second-stage payload (the technical term) actually being downloaded. According to the vendor, however, the compromised version did contain tools for remote code execution.

Image source: AI-generated (November 2026)

Translated from the German original using artificial intelligence. The German version is authoritative.

Further reading

A magazine by Evernine Media GmbH