← Back to context Comment by pkulak 6 hours ago How could this happen to a project with 55k commits in three years? 8 comments pkulak Reply Aurornis 5 hours ago 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. crossroadsguy 6 hours ago Every harness thinking right now… "if we want do something like this we won't even have to compromise anything." zargon 6 hours ago Sarcasm? pkulak 6 hours ago haha, yes, sorry. rirze 6 hours ago you needed more exclamation marks :) 3 replies →
Aurornis 5 hours ago 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.
crossroadsguy 6 hours ago Every harness thinking right now… "if we want do something like this we won't even have to compromise anything."
zargon 6 hours ago Sarcasm? pkulak 6 hours ago haha, yes, sorry. rirze 6 hours ago you needed more exclamation marks :) 3 replies →
pkulak 6 hours ago haha, yes, sorry. rirze 6 hours ago you needed more exclamation marks :) 3 replies →
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 :)
3 replies →