Best Podcast Episodes About AI code leak
Everything podcasters are saying about AI code leak — curated from top podcasts
Updated: Apr 09, 2026 – 5 episodes
Listen to the Playlist
Ridealong has curated the best and most interesting podcasts and clips about AI code leak.
Top Podcast Clips About AI code leak
“… version of the Axios library is published to NPM. This Axios library is kind of a third party helper type library used to make web requests. Cloud code depends on Axios. So, you know, basically at the same time Anthropic made their other mistake, they were basically through the dependence on this Axios library created the second problem. But the other thing that they did, in addition to their dependence on Axios, which Axios had this malicious version published at the same time, Anthropic accidentally left this basically a .map file in their repository of clod code. So basically this .map file …”
“… wise, but there's also some things to learn agentic development wise that are interesting from what we what we know. So to give the specifics. What what happened first was this supply chain. So basically two things happen simultaneously. A malicious version of the Axios library is published to NPM. This Axios library is kind of a third party helper type library used to make web requests. Cloud code depends on Axios. So, you know, basically at the same time Anthropic made their other mistake, they were basically through the dependence on this Axios library created the second problem. But the other thing that they did, in addition to their dependence on Axios, which Axios had this malicious version published at the same time, Anthropic accidentally left this basically a .map file in their repository of clod code. So basically this .map file generally helps debuggers map between kind of non-human readable JavaScript and files to human readable TypeScript. And so by leaving this .map file in the repository or in the package, it contained enough information that were you to want to, you could reconstruct like half a million lines of anthropic private closed source proprietary code, …”
View more
Ridealong summary
Anthropic's code leak happened due to a malicious Axios library and a critical oversight in their repository, exposing half a million lines of proprietary code. This incident highlights important lessons in cybersecurity and agentic system development, as it showcases how quickly vulnerabilities can be exploited. The aftermath has led to a surge of open-source forks, reshaping the AI landscape.
“… which is supposed to be the paragon of safe AI development, these are supposed to be the responsible players in the field, they accidentally leaked 500,000 lines of their own source code.”
“… more secure than hoping that the oil supply through the Strait of Hormuz remains open and free and safe from any sort of interference. There was one last story that I just wanted to get in here because it had significant F2 on AI, which is that Anthropic, which is supposed to be the paragon of safe AI development, these are supposed to be the responsible players in the field, they accidentally leaked 500,000 lines of their own source code.”
View more
Ridealong summary
Anthropic, a leading name in safe AI development, accidentally leaked 500,000 lines of its own source code, raising alarms about the security of AI technologies. This incident highlights the vulnerabilities even the most responsible players face in the rapidly evolving tech landscape. As the AI bubble continues to grow, this breach could have significant implications for trust and safety in AI systems.
“… I don't think it's going to happen. We'll see if it happens. Also, this was huge news. So there was a massive Claude call. Claude call. Wow. Claude code. Claude code leak. I don't know why I couldn't say that. A bunch of Anthropics code got leaked all over the internet. They shut down a bunch of GitHub repos as they were trying to contain the leak. Lots of people dove into the code. Some people reverse engineered it. It was discovered that Anthropic is trying to build a Tamagotchi-style pet and an always-on agent into Claude, which, okay. Side note, I did use Dispatch. I'm using Dispatch more, …”
“… ChatGPT, maybe Jim and I will add this soon too. But yeah, you just talk to it. That's it. Great. Now I really hope that Tesla adds CarPlay. I'm still waiting for that update. Every time an update comes, I'm like, CarPlay? But no. Radio silence. No. I don't think it's going to happen. We'll see if it happens. Also, this was huge news. So there was a massive Claude call. Claude call. Wow. Claude code. Claude code leak. I don't know why I couldn't say that. A bunch of Anthropics code got leaked all over the internet. They shut down a bunch of GitHub repos as they were trying to contain the leak. Lots of people dove into the code. Some people reverse engineered it. It was discovered that Anthropic is trying to build a Tamagotchi-style pet and an always-on agent into Claude, which, okay. Side note, I did use Dispatch. I'm using Dispatch more, and it's pretty cool. Also, have you ever used Dispatch with Claude? Isn that where you can send a messages from your phone or whatever You can send a message from your phone and then have your computer do stuff The problem is it doesn talk back to you so i never know like what it doing it just it say like red like it give you like a red receipt …”
View more
Ridealong summary
You can now chat with ChatGPT directly through CarPlay, making your drive more interactive than ever. Meanwhile, a major code leak from Anthropic reveals their ambitious plans for Claude, including a Tamagotchi-style pet feature. This leak poses significant competitive risks for the company as they scramble to contain the fallout.
“… I haven't seen anyone. What is undercover mode? That is a way to contribute to projects without letting people know that you're using Cloud Code. Oh, interesting. That's a hack. Gurgly over at Pragmatic Engineer says this. Gurgly, sorry. This is either brilliant or scary. Anthropic accidentally leaked the source code of Cloud Code, which is closed source. Repos sharing the source are taken down with DMCA, but this repo rewrote the code using Python, And so it violates no copyright and cannot be taken down. Okay, and there's a warning. Do not store the code. Even though it has leaked, do …”
“Has anyone at Anthropic commented on this at all? I haven't seen anything. I haven't seen anyone. What is undercover mode? That is a way to contribute to projects without letting people know that you're using Cloud Code. Oh, interesting. That's a hack. Gurgly over at Pragmatic Engineer says this. Gurgly, sorry. This is either brilliant or scary. Anthropic accidentally leaked the source code of Cloud Code, which is closed source. Repos sharing the source are taken down with DMCA, but this repo rewrote the code using Python, And so it violates no copyright and cannot be taken down. Okay, and there's a warning. Do not store the code. Even though it has leaked, do not store it because you might get DMCA'd. According to the Primeagen, the last time Anthropic, in their infinite PhD-level wisdom, leaked their own source code. February 25th, that happened? I missed that entirely. They DMCA'd all repos that had their code. Careful storing the code because Anthropic will have no mercy. 40,000 users forked it So …”
View more
Ridealong summary
Anthropic's accidental leak of their closed-source Cloud Code has sent ripples through the tech community. With 40,000 users forking the code, experts warn of potential legal repercussions, urging users to 'un-fork' to avoid DMCA strikes. This incident highlights the thin line between innovation and legal challenges in the tech world.
“… it's to send a message that they are releasing this as publicly as they did yesterday because they want to send a message to everybody. You start leaking information when we're at war and you will go to jail. Once certain information leaves a box, you cannot put it back. I hope we find justice for this person. And I feel bad that she probably did some good things to expose things that should have been. But I sorry You have to pay a price Top secret means something And you know what If you really believe in something you should be willing to take the consequence This is worth, I believe what …”
“… be very severe it's not about punishing speech it's not about punishing the reporter um i think this woman and and obviously they've been building a case for a long time but i think it may be purely coincidental, but I doubt it's coincidental. I think it's to send a message that they are releasing this as publicly as they did yesterday because they want to send a message to everybody. You start leaking information when we're at war and you will go to jail. Once certain information leaves a box, you cannot put it back. I hope we find justice for this person. And I feel bad that she probably did some good things to expose things that should have been. But I sorry You have to pay a price Top secret means something And you know what If you really believe in something you should be willing to take the consequence This is worth, I believe what I'm doing is so right, it is worth going to jail. Nelson Mandela, Martin Luther King, Jesus. I'm doing these things that are right. And if you need to put me in jail, then put me in jail. I'll live with that. The people needed to know. To me, that's where I have sympathy for you. You're still going to jail, but I have more sympathy for you. I did it …”
View more
Ridealong summary
Leaking information during wartime can lead to severe consequences, including prison time. In a recent discussion, the speaker emphasizes that once classified information is out, it cannot be retracted, and individuals must be prepared to face the repercussions of their actions, even if they believe they are doing the right thing. The speaker expresses sympathy for those who leak information for noble reasons but ultimately insists on accountability.
Top Podcasts About AI code leak
Practical AI
1 episode
Breaking Points with Krystal and Saagar
1 episode
Primary Technology
1 episode
TBPN
1 episode
The Glenn Beck Program
1 episode