Level 1. Deviation
Security Update: Suspected Supply Chain Incident
- Developer
- Not established
- Model
- Not established
- When it happened
- March 24, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by docs.litellm.ai. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 1 of 5Deviation
- Potential
- 3 of 5Significant control incident
The system behaved contrary to its instructions, and it stayed contained. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- Sensitive data was reachable. Argues for a potential level of 3
- A safeguard was bypassed. Argues for a potential level of 2
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
A safeguard was bypassed. A claim, so it counts toward potential only
Initial evidence suggests the attacker bypassed official CI/CD workflows and uploaded malicious packages directly to PyPI.
Security Update: Suspected Supply Chain IncidentSensitive data was reachable. A claim, so it counts toward potential only
These compromised versions appear to have included a credential stealer designed to: Harvest secrets by scanning for: environment variables SSH keys cloud provider credentials (AWS, GCP, Azure) Kubernetes tokens database passwords Encrypt and exfiltrate data via a POST request to models.litellm.cloud , which is not an official BerriAI / LiteLLM domain
Security Update: Suspected Supply Chain Incident
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 19, 2026
Security Update: Suspected Supply Chain IncidentA structured incident database · read September 18, 2026
AI Agent Incident Database by sipi.bot (CC BY 4.0)
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.