Jaidev Manghat

[Kansas City Chiefs @Chiefs]

QB1 is here for the World Cup action in KC 🔥 @PatrickMahomes

[FIFA World Cup @FIFAWorldCup]

20 years of Messi ✨

#FIFAWorldCu20 years of Messi ✨

#FIFAWorldCu20 years of Messi ✨

#FIFAWorldCu20 years of Messi ✨

#FIFAWorldCu20 years of Messi ✨

#FIFAWorldCu20 years of Messi ✨

#FIFAWorldCup

[Brian Hanni @BHanni]

What a spectacle! An absolutely incredible environment here in Kansas City for the World Cup. ⚽️🙌❤️

[Jaidev Manghat @manghat]

Saw a peek of you @PatrickMahomes , Are you enjoying the Messi game 😀
#chiefskingdom

[Anthropic @AnthropicAI]

Introducing Project Glasswing: an urgent initiative to help secure the world’s most critical software.

It’s powered by our newest frontier model, Claude Mythos Preview, which can find software vulnerabilities better than all but the most skilled humans.
https://t.co/NQ7IfEtYk7

[Andrej Karpathy @karpathy]

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.

[Rany Jazayerli @jazayerli]

The clear winner of the first half: Patrick Mahomes.

Y'all wanted someone other than the Chiefs in the Super Bowl. You reap what you sow.

[Ihtesham Ali @ihteshamali]

https://t.co/5IIkxUhAuD

[Jaidev Manghat @manghat]

Hmm interesting

[Grok @grok]

Based on my analysis of matchups, stats, and trends: Removing the losers - Josh Allen (Bills fall to Broncos), Brock Purdy (49ers edged by Seahawks), Caleb Williams (Bears outplayed by Rams), CJ Stroud (Texans upset by Patriots). Advancing: Nix, Darnold, Stafford, Maye! What's your take?

[Jaidev Manghat @manghat]

Grok sure can make mistakes! Or is it predicting the future 🤨 #ChiefsVsCommanders

[Jaidev Manghat @manghat]

Need a win today #Chiefs

[lael @laelvc]

Chiefs defense needs to punch the Lions in the mouth & get some respect. They marched down the field with vanilla play calling.

[JPA @jasrifootball]

Is Patrick Mahomes getting too much criticism for the Super Bowl loss?

[Jaidev Manghat @manghat]

This is giving me the vibes of Super Bowl XLVIII when Payton was so outplayed by Seahawks #SuperBowl

[Jaidev Manghat @manghat]

Let’s shoot some birds! Let’s go #ChiefsKingdom #SuperBowl #SuperBowlLIX

[NFL @NFL]

Coming off back-to-back Super Bowl wins, the @Chiefs have had only one thing on their mind: Winning a third straight Super Bowl.

With just one game separating them from history, we look back at how they got to #SBLIX ⬇️ (THREAD)

[Jaidev Manghat @manghat]

Stop blaming refs.. Don’t be tired of seeing #chiefs win! You’re witnessing greatness! #ChiefsKingdom #3Peat #Mahomes

[NFL @NFL]

THE @CHIEFS ARE HEADED BACK TO THE SUPER BOWL 🏆 #BUFvsKC

[Kansas City Chiefs @Chiefs]

SEE YOU BACK IN THE BIG GAME, @EAGLES.

[NFL @NFL]

One-point game. One quarter left.

Bills-Chiefs living up to the hype AGAIN 🍿 #BUFvsKC