lol oh my god i feel **so fucking smug** right now, it's incredible.

[peter@thepit.social]

@gfitzp oh nooooo

[peter@thepit.social]

based on some commits in the repo, seems like it was these guys: https://arstechnica.com/security/2026/03/self-propagating-malware-poisons-open-source-software-and-wipes-iran-based-machines/

[gfitzp@social.glennfitzpatrick.com]

@peter Yup, I was like "didn't I just read about these guys like an hour ago??"

[mkristensson@thepit.social]

@peter and @dangoodin sometimes hangs out here

[peter@thepit.social]

picking through the various bits and pieces of this story, i kind of think what really happened is the dev accounts got pwned, and then the attackers were able to push a bad version to PyPi and people pip installed it from there. so as far as a "supply chain" attack, LiteLLM is the part of the supply chain that got attacked, it's not like they accidentally vibe-coded something malicious into their project.

[jongary@macaw.social]

@peter it isn’t even necessary to compromise repos. If a malicious actor posts enough malicious code that gets mingled with the LLM training data, some poor souls will start vibe-coding malicious code directly into their own products.

[peter@thepit.social]

but this still goes back to what i was saying: this AI ecosystem is developing **way** too fast and without the kind of maturity that is naturally required when you have lots of people working on a thing. so with berri.ai, you had ~2 guys in their 20s building this thing at break-neck speed that became the linchpin to waaaaay too much of the "AI" ecosystem and now look what's happened.

[peter@thepit.social]

@jongary 100%!!

[tael@yiff.life]

@peter The crypto wallet checker in this compromise really underlines the fact that there's so much overlap between LLM boosters and crypto boosters. It's all the same marks. They just found something easier to sell to people.

[peter@thepit.social]

@tael i think also, banks and payment processors have made it so much more difficult to steal and do anything with credit card numbers that there's not much point in going after those anymore, especially when finding someone's crypto passphrase is like picking up money off the ground.

[spinnyspinlock@infosec.exchange]

@peter oh my a day ending in -y

[davidgerard@circumstances.run]

@peter @tante @briankrebs thank you for this comedy gold

[tael@yiff.life]

@peter It's easy to siphon crypto, yeah, but turning that into spendable money has gotten much, much more difficult than it used to be.

[nan@mastodon.green]

@peter is wrapping a vibe coded mess into a package so it looks reasonable the new sub-prime mortgage?

[davidgerard@circumstances.run]

@peter @tante @briankrebs we've replaced Jia Tan with a very small prompt

[alessandro@cosocial.ca]

@peter

That xkcd comic with the stacked blocks, but instead of one guy in Nebraska, it's LLM slop.

[dogiedog64@app.wafrn.net]

@tante@tldr.nettime.org @davidgerard@circumstances.run @briankrebs@infosec.exchange @prietschka@mastodon.social @peter@thepit.social

@prietschka You're gonna get a laugh out of this one, methinks.

[davidgerard@circumstances.run]

@dogiedog64 @tante @briankrebs @prietschka @peter lol god yes he will

[slab_bulkhead@mastodon.online]

@peter Semi-related: anyone know why that issue had hundreds of bot replies like "this worked for me"? Is that reputation farming or an active strategy to bury important information in slop?

[wordshaper@weatherishappening.network]

@peter I am, for one rare moment, actually glad to read the HN comments. The one from the dude complaining that blocking all downloads of the compromised package breaks all his setups because they're written to automatically pull a bunch of packages off the net every time they start was... :chefskiss: