Shristi Shukla

30 posts

Shristi Shukla

@session_timeout

Build & Ship ! | https://t.co/kGSytSDpkm

Bangalore 参加日 Haziran 2025

115 フォロー中19 フォロワー

Shristi Shukla@session_timeout·11 Nis

Chapter 7 🫶🏻

The Residency - Bangalore House@residencyBLR

LIVE demos across across AI, hardware, fintech, sustainability... we had it all. we just hosted our BIGGEST demo day at @residencyBLR with 15 pitches, 80+ VCs & 300+ attendees. the whole ecosystem showed up to support and witness what our founder have been upto. momentum compounds, and this demo day was a big acceleration forward in achieving the mission we set out for ourselves - becoming home to India’s most ambitious. to the upcoming cohort, we’ll be ready for ya’ll in June’26 @theresidency stay tuned 🫶 thank you for believing in us: Together fund, @The_Zo_World, @inklehq, @aoagents, @thelaunchd , no cap foods and @DrinkQuenzy and to the team who made it all possible: @AadityaYuvraj, @NimishaChanda, @M_S_MIHIR, @ashmitharamya, @GarimaShhh, @sherlock_ux and Aayush

English

Shristi Shukla@session_timeout·31 Mar

@PossiblyTejas @yoitsmanan @prithvireddy_dr @niraj_munot @AadityaYuvraj @residencyBLR Whaattaaa day !

English

133

Tejas Agrawal@PossiblyTejas·28 Mar

coolest guy with the coolest team

Nimisha Chanda@NimishaChanda

coolest guy at the @residencyBLR demo day!

English

1.4K

Shristi Shukla がリツイート

The Residency - Bangalore House@residencyBLR·28 Mar

honestly, where else do you see - - 15 product demos in one night? - a 17-year-old, a 19-year-old, and a 40-year-old all building in the same room like it's the most normal thing in the world? - 150 people who didn't have to show up - but did? - 50+ investors not just watching, but actually closing deals that night? - and a live band at the end because why not, haha! that's just @theresidency bangalore for y'all.

Nimisha Chanda@NimishaChanda

we just hosted the final demo day for our latest cohort @residencyBLR for the past 3 months, a group of builders lived and worked together under one roof for our cohort @theresidency bangalore. every week, they showed up for internal demo days. > what did you ship > what changed > what actually moved forward and now, this was the final showcase. we had 700+ registrations around 150 people were in the room! builders, operators, and 50+ investors coming in to see what was built the range of ideas still surprises me and i don't think if i would ever be able to build something this good myself. from LLM intelligence for drones, to tools for options trading, to a cybersecurity product built by someone who has worked on Chandrayaan this is what the residency does well - it compresses time. in a few months, you can go from idea to product from product to users from users to being investment ready :) we’ve seen it happen before too. > founders raising their first $100k > startups hitting early traction > people flying to SF to take things further but what stands out is not just the outcomes. it’s the pace. the environment. the constant pressure to build and show up every single week. demo day is just a snapshot. the real story is everything that happens before it! so grateful to be a part of something like this :)

English

3.2K

Shristi Shukla がリツイート

Andrej Karpathy@karpathy·24 Mar

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.

Daniel Hnyk@hnykda

LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below

English

1.4K

5.4K

28.1K

66.5M

Shristi Shukla がリツイート

The Residency - Bangalore House@residencyBLR·25 Şub

A $5T economy goal needs more than ambition. It needs builders. It needs entrepreneurs. People who can build defence tech, drone systems, AI infra, consumer AI… and everything India hasn’t seen yet. That’s why @residencyBLR exists. Look at our Week 3 demo day hosted with @scaletogether where the builders get real-time feedback on their projects and start becoming real, scalable companies.

English

1.7K

Shristi Shukla@session_timeout·13 Mar

Bangerrrrr ! @AskBaluBabu

Balu Babu@AskBaluBabu

Most incident tools tell you when something breaks. Vader helps engineering teams understand the what, how, why, and when. Incident investigation for modern teams. Join the waitlist for free platform credits: usevader.dev Thank you @residencyBLR @theresidency for the support from day 1.

Indonesia

Shristi Shukla@session_timeout·3 Şub

@Ashf03 LFGGG ! ✨

Ash@Ashf03·2 Şub

Aquin is out. vibe code your LLM in 2 mins.

English

162

15.3K

Shristi Shukla@session_timeout·1 Şub

And drove me back home without getting mad with the navigation 😬

Tejas Agrawal@PossiblyTejas

Spent the day at AI Engineers Day with @OpenAI , @peakxvpartners, and Activate, along with fellow founders from @residencyBLR . Got to personally talk to the OpenAI team, picked up a lot of real learnings, and yes, walked away with OpenAI credits and stickers.

English

125

Shristi Shukla@session_timeout·1 Şub

@DawaneManasvi @Pushkar11420566 @Ashf03 @PossiblyTejas @virakti150 @GarimaShhh @PossiblyTejas always to the rescue !

English

Manasvi dawane@DawaneManasvi·30 Oca

Backbenchers 😎 last minute things @Pushkar11420566 @session_timeout rescue operation by @Ashf03 @PossiblyTejas @virakti150 @GarimaShhh 🍿

English

131

Shristi Shukla@session_timeout·22 Oca

Heheh , was so much fun doing this !

Ash@Ashf03

The @theresidency network

English

105

Shristi Shukla@session_timeout·12 Oca

@AadityaYuvraj @residencyBLR @theresidency @NimishaChanda @BLRxZo LFFGGGG , The Next Big Thing !

English

Yuvraj Aaditya@AadityaYuvraj·12 Oca

Started with a bang! @residencyBLR chapter 7 orientation

English

118

9.9K

Shristi Shukla がリツイート

BLANK — oss/acc@blank_spacets·2 Oca

blank.aryank.space

ZXX

193

Shristi Shukla がリツイート

AluanWang@IOivm·17 Kas

The hardest thing? Keeping it simple.

English

178

2.2K

59.5K

Shristi Shukla@session_timeout·23 Ara

@snoopy_dot_jpg Been there , done that

English

Shristi Shukla@session_timeout·20 Ara

@mehulmpt Can't get over this fr bloomberg.com/news/newslette…

English

4.7K

Mehul Mohan@mehulmpt·20 Ara

It’s interesting how Amazon was able to figure out that an employee was working from North Korea based on keystroke latency between physical keypress and actual keystroke retrieved on server. Hard to beat physics.

English

235

1.3K

37.6K

2.5M

Shristi Shukla@session_timeout·20 Ara

@gothburz Dayumm , krazy one !

English

Peter Girnus 🦅@gothburz·19 Ara

My CISO called me at 3 AM last Tuesday. "We caught someone." I asked, "Caught them doing what?" He said, "Typing." Let me explain. We have an employee in IT. Great worker. Always online. Never complained. Perfect Slack etiquette. One problem. His keystrokes were arriving 110 milliseconds late. One hundred and ten milliseconds. That's 0.11 seconds. The average American remote worker has 20-40ms of latency. This guy? 110ms. Every. Single. Keystroke. My security team ran the numbers. That latency doesn't come from a bad router in Ohio. That latency comes from Pyongyang. Our "Senior DevOps Engineer" was a North Korean operative. Running his work laptop through a laptop farm. In America. While he worked from a government building. In North Korea. He passed the interview. He passed the background check. He passed the vibe check. He did not pass the speed of light. Here's what people don't understand about physics: Light travels 186,000 miles per second. But it still has to go through China. And China adds latency. Since April, Amazon has caught 1,800 of these attempts. Eighteen hundred. I called an emergency meeting with my board. I said, "We need to implement Keystroke Velocity Auditing across all remote employees." They said, "That sounds invasive." I said, "You know what else is invasive? The Democratic People's Republic of Korea in your Jira tickets." They approved the budget. We now monitor keystroke timing to the microsecond. If your latency exceeds 60ms, you get a call from HR. If it exceeds 100ms, you get a call from the FBI. We've already flagged 47 employees. Turns out 44 of them just have bad Wi-Fi. 3 of them are "still under investigation." The lesson? You can fake a resume. You can fake a background check. You can fake an American accent on Zoom. But you cannot fake the speed of light. Physics is the ultimate background check. Hire accordingly.