
Andrés Snitcofsky
6.2K posts

Andrés Snitcofsky
@ams
Fan de @cliengo y @Leadaki más en https://t.co/f8u0Fjs1Qw, y no soy @rusosnith







Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.








Big news for fútbol fans: Apple Sports is now available in Latin America and the Caribbean! You can check real-time scores and stats from your favorite leagues, right on your iPhone.

Recorded my first walkthrough video for App Publishing via @ManusAI 👉👈✨ You can now package and share your app for testing on @GooglePlay Store and the @Apple App store without setting up Xcode, Android Studio, or wrestling with build configurations. Supported platforms: • Android → Google Play (Internal Testing) • iOS → App Store (TestFlight) Ready to try it? Here's how 👇 ➡️Google Play: Prerequisites: Google Play Developer account ($25 one-time fee) Steps: 1. In Manus, click Publish → select the Android tab 2. Click Build APK — Manus packages your app in AAB format 3. Go to your Google Play Console and navigate to Internal testing 4. Click Create new release and upload the AAB file 5. Under Testers, add your email address (or create an email list for your team) 6. Copy the opt-in link 7. Open the link on your Android device, accept the invite, and install ➡️App Store: Prerequisites: • Apple Developer account ($99/year) • iPhone with TestFlight installed Steps: 1. In Manus, click Publish → select the iOS tab 2. Click Create app and follow the prompts to connect your Apple Developer account 3. Manus will package and upload your app to App Store Connect automatically 4. Wait for Apple to process your build 5. You'll receive an email from TestFlight when it's ready 6. Open the email on your iPhone, tap the link, and install via TestFlight 🔗 Full guide: help.manus.im/en/articles/13… Let me know what else you'd like to see next!



🚨 NEW LABS EXPERIMENT 🚨 Introducing CC, an experimental AI productivity agent in Gmail. Get a “Your Day Ahead” briefing every morning in your inbox and email CC anytime for help. Sign up for early access in the US & Canada. We’ll be starting with Google AI Ultra and paid subscribers. ⬇️ labs.google/cc







