Skip to main content
Mallory
← Back to News
package-repository-poisoningcredential-stealer-activitybuild-pipeline-compromiseleaked-secret-api-key

LiteLLM Hit by PyPI Supply-Chain Compromise and Guardrail Sandbox Escape

Supply Chain Risk · 5 sources · Updated 5mo ago · First seen Mar 27, 2026

LiteLLM Hit by PyPI Supply-Chain Compromise and Guardrail Sandbox Escape

Datadog Security Labs reported that the TeamPCP supply-chain campaign compromised the legitimate PyPI package LiteLLM, publishing malicious versions 1.82.7 and 1.82.8 that stole credentials, exfiltrated data, established persistence, and in some cases attempted to spread into Kubernetes environments. The campaign also hit Telnyx on PyPI and was linked to earlier compromises involving Trivy, npm packages, Aqua Security repositories, and Checkmarx tooling, with researchers concluding that stolen CI/CD and publishing credentials were reused across ecosystems. Datadog warned that LiteLLM 1.82.8 was especially dangerous because a malicious .pth file triggered payload execution when the Python interpreter started, while the Telnyx package executed code at import time and retrieved a second-stage payload hidden in a WAV file.

Separately, X41 disclosed a high-severity sandbox escape in BerriAI LiteLLM affecting the main-latest Docker image, where authenticated users could reach arbitrary code execution through the /guardrails/test_custom_code API endpoint. The flaw relied on bypassing regex-based restrictions on custom Python guardrail code using string concatenation and CPython bytecode rewriting to recover unrestricted builtins and call __import__, allowing commands to run as the LiteLLM process user, which is root in the default Docker deployment. X41 assigned the issue CWE-94 and a CVSS 4.0 score of 8.7, and Datadog advised organizations that installed the malicious LiteLLM releases to treat affected hosts and CI jobs as full credential-exposure events, rotate secrets, hunt for persistence and outbound traffic, and rebuild critical systems from known-good images rather than relying only on package rollback.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

7 events · Feb 3, 2026 – Apr 15, 2026
  1. Apr 15, 20267mo ago

    Gurucul identifies Mercor as downstream victim of LiteLLM compromise

    Gurucul reported that the malicious LiteLLM supply-chain compromise impacted downstream users, including Mercor, where the compromised dependency enabled unauthorized data access and possible command execution. The report framed Mercor as a case study of the breach's downstream effects.

    LiteLLM Supply Chain Compromise: Downstream Impact Analysis with Mercor Breach Case Study | Community Portal | Gurucul
  2. Apr 15, 20267mo ago

    LiteLLM releases version 1.83.10 to fix guardrail RCE flaw

    Zenity reported that LiteLLM version 1.83.10 was released to fix CVE-2026-40217, a sandbox-escape remote code execution issue in the /guardrails/test_custom_code endpoint affecting versions 1.81.8 through 1.83.9. The report says exploitation attempts began the same day the fix was released.

    Threat Actors Are Trying to use LiteLLM's Guardrail Tester to Run Code as Root
  3. Mar 27, 20268mo ago

    Malicious Telnyx releases 4.87.1 and 4.87.2 published to PyPI

    Attackers also compromised the legitimate Telnyx Python package on PyPI, publishing malicious versions 4.87.1 and 4.87.2. The package executed malicious code at import time and retrieved a second-stage payload concealed in a WAV file.

  4. Mar 24, 20268mo ago

    Datadog links LiteLLM and Telnyx compromises to TeamPCP campaign

    Datadog Security Research reported that the PyPI compromises of LiteLLM and Telnyx were part of the broader TeamPCP supply-chain campaign, which had previously affected Trivy, npm packages, Aqua Security repositories, and Checkmarx tooling. The report said stolen CI/CD and publishing credentials were reused across ecosystems to expand the campaign.

  5. Mar 24, 20268mo ago

    Malicious LiteLLM releases 1.82.7 and 1.82.8 published to PyPI

    As part of the TeamPCP supply-chain campaign, attackers compromised the legitimate LiteLLM package on PyPI and published malicious versions 1.82.7 and 1.82.8. Datadog assessed version 1.82.8 as especially dangerous because a malicious .pth file triggered payload execution at Python interpreter startup.

  6. Feb 13, 20269mo ago

    X41 publicly discloses unpatched LiteLLM RCE vulnerability

    X41 D-Sec published advisory X41-2026-001 describing a LiteLLM sandbox escape that could lead to arbitrary code execution as the LiteLLM process user, which is root by default in the affected Docker image. At publication, no patch was available.

  7. Feb 3, 202610mo ago

    X41 reports LiteLLM guardrail sandbox escape to vendor

    According to the advisory's disclosure timeline, X41 D-Sec privately reported a high-severity sandbox escape in LiteLLM's /guardrails/test_custom_code endpoint in February 2026. The flaw allowed authenticated users to bypass source filtering and achieve arbitrary code execution in the default Docker deployment.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Threat actors

1 linked

Affected products

2 linked
LitellmLitellm

Organizations

2 linked
LitellmTelnyx

Breaches

1 linked
LITELLM-2026-03

Observables

24 linked

Indicator values are masked on this page. View all 24 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.