How could this happen to a project with 55k commits in three years?
The compromise appears somewhere in the build and deploy system.
> No public commit in BerriAI/litellm contains data = "cook" or a cook/ folder.
> SafeDep assesses, with moderate to high confidence, that BerriAI’s private release pipeline built these wheels from an attacker-modified git source.
Every harness thinking right now… "if we want do something like this we won't even have to compromise anything."
Sarcasm?
haha, yes, sorry.
you needed more exclamation marks :)
The gentleman's /s tag.
I mean, 55k commits in 3 years, that's about 55 a day, 7 days workweek. It's reasonably implied no one can be looking at all them thoroughly.
This incident is unrelated to what was committed to the repository. More info: https://docs.litellm.ai/blog/security-incident-oct-21-2026
The compromise appears somewhere in the build and deploy system.
> No public commit in BerriAI/litellm contains data = "cook" or a cook/ folder.
> SafeDep assesses, with moderate to high confidence, that BerriAI’s private release pipeline built these wheels from an attacker-modified git source.
Every harness thinking right now… "if we want do something like this we won't even have to compromise anything."
Sarcasm?
haha, yes, sorry.
you needed more exclamation marks :)
The gentleman's /s tag.
I mean, 55k commits in 3 years, that's about 55 a day, 7 days workweek. It's reasonably implied no one can be looking at all them thoroughly.
This incident is unrelated to what was committed to the repository. More info: https://docs.litellm.ai/blog/security-incident-oct-21-2026