My minute-by-minute response to the LiteLLM malware attack
An Internet, an employee of Futuresearch.ai (business model: 'Uber for transcript generation'), accidentally becomes patient zero for a malware package after the latest version of litellm, a critical dependency for his "AI workflow," tries to turn his laptop into a cryptomining botnet disguised as a fork bomb, a process which he documents in real time by asking another AI to explain what he's asking it to do. PyPI (business model: 'Uber for cryptographically signed malware') eventually quarantines the package, a heroic act that prevented the malware from being served to six strangers per day, while Hackernews debates whether writing "native code" or just using Emacs would have magically prevented this outcome that is inherent to the towering edifice of dependencies they all require to serve text files. The only real solution, according to Hackernews, is for package managers to add "cooldown" timers, or for more AIs to watch the AIs that are writing the packages that the other AIs are pulling in, creating an infinite recursion of automated babysitters for a supply chain that everyone knows is made of glass. In the end, the collective shrug is punctuated by one Hackernews sincerely thanking the original Internet for his service, a sentiment usually reserved for people who face actual danger and not just a corrupted `litellm_init.pth` file.