cross-posted from: https://lemmy.ml/post/45529149
Here is the message where he found out what happened:
I didn’t receive any information about it but when creating a support ticket I was told my account has been flagged and I had to do some extra verification. I’ve created a support ticket now and will keep you posted. I’ll believe it’s nothing major though, I use 2FA everywhere, the last commit on all repos is what I expect, and all sessions and usages look fine
Absolutely fuck Github and Microslop, they can just vanish your projects without notice whenever they want with barely any justification for it, and then take their sweet time to fix it too.
VLLMlitellm supply chain attack.Creator possibly was compromised and likely a security measure.
Affected versions were not pushed IMO, but the owners machine may have been compromised.
No, my whole account has been set to private. KitchenOwl never contained the malicious versions of litellm. The last pinned versions in the lock file on the dev branch were 1.82 and with the latest release 1.83. Sadly, GitHub just decided to flag my account and set it to private without notifying me… I’m waiting for a support response.
Glad to hear! Thanks for giving some info.
Still could be some half baked github response. Not saying it’s actually the case, but a possibility.
Hoping you can get a timely response and your account back!
How do you know that?
I do not know for sure, but the repo did contain the dependency litellm with version specifier >=1.65.0 (if I recall correctly) and an early march build did use the version 1.81.0 per the uv.lock (version before the compromised litellm==1.82.7 and litellm==1.82.8 )
https://docs.litellm.ai/blog/security-update-march-2026
Not saying that the Dev was compromised, but it is possible, and it could be some Github precaution to disable repos with that dependency where a
pip installat the wrong time could have compromised all the Devs credentials.