Litellm versions 1.82.7 and 1.82.8 on PyPI have been compromised with a forkbomb payload. Python devs, check your requirements.txt before your servers crash.
Just a normal Tuesday, setting up a fresh project, and suddenly your laptop sounds like it's preparing for takeoff. To all the Python devs and AI wrappers out there: we have a massive breach on PyPI.
So, a fellow dev dropped a nuke on Hacker News recently: Litellm versions 1.82.7 and 1.82.8 on PyPI are officially compromised.
The OP was just doing a standard setup when their machine's RAM got instantly devoured. Classic forkbomb behavior—spawning dummy processes until the OS chokes and dies.
Sensing some black magic, they dug into the source code and found a sketchy base64-encoded blob chilling inside proxy_server.py. What does it do? It silently writes, decodes, and executes another malicious file in the background. Absolute madlads, but definitely not the good kind. OP immediately flagged this upstream to the BerriAI team to stop the bleeding.
Whenever a supply-chain attack hits, the tech community usually splits into three distinct tribes:
pip install package_name without locking down the version, you're basically playing Russian roulette with your codebase.Look, guys, open-source is great until it bites your head off. You can't just blindly trust everything you pull from the internet.
The takeaway? Pin your damn dependencies. And when you're testing new or suspicious packages, isolate them. Run them in Docker, or even better, grab a Free $300 to test VPS on Vultr to safely blow things up without nuking your daily driver or company servers. Sandboxing is your best friend.
Check your requirements.txt ASAP. If you're on Litellm 1.82.7 or 1.82.8, downgrade immediately and kill those rogue processes!
Source: GitHub Issue - Litellm