Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

The OpenSourceMalware Show

The OpenSourceMalware Show artwork

Keyv and Cachable maintainer talks about ChainDrop attack

Nov 13, 20261 hr 8 minAudio

This week we had a special guest on the show: Jared Wray, who is the maintainer of several popular open source projects, including Keyv and Cacheable. In August 2026, he was the victim of an account takeover. A threat actor used a GitHub token he thought he'd retired to push malware into his Kevy and Cachable, and his own release pipeline shipped it to npm with valid provenance. It contained a worm that propagated the malware into 400+ npm packages. The campaign became known as ChainDrop, and the worm code was based on TeamPCP's open-sourced Mini Shai-Hulud worm. We talked about: How the attack happened Getting his accounts back Rebuilding his setup Security controls that are harder than they sound Vetting new dependencies Staying on GitHub Actions Episode resources: (webpage) Jared Wray on GitHub (blog) New npm Worm Hits 400+ Packages Including Keyv, Cachable (blog) Keyv and Cacheable - Chaindrop Worm (blog) Coding Securely in the Age of AI

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Jenn GileHello, it is Thursday, November 12th. I'm Jen Gile. I have Paul McCarty with me. We're the host of the open source malware show. And we're excited to have a special guest with us today. Jared Ray is the uh maintainer of, I did some math before, over 60 uh open source packages, totaling, we think, if the agents are right, uh a billion weekly downloads. And he has the uh, I guess, unfortunate pleasure to have been the victim of a software supply chain attack earlier this year that resulted in a whole bunch of packages getting infected uh on NPM, which we'll talk about in just a moment.

Jenn GileBut Jared, uh why don't you give a quick intro for yourself?

SPEAKER_00Uh great. Yeah, thanks for having me on. Uh Jared Ray, uh entrepreneur. I've done multiple companies. Uh also uh started doing open source just about a decade ago, uh really just giving back to the community and things like that. Um I'm the CEO of Hyphen, which is an uh AI-based agent for DevOps.

Jenn GileAnd you uh are no stranger to engineering, you're a recovered CTO yourself.

SPEAKER_00Yeah, yep. Yeah. I've been CTO in many companies, uh, from streaming media companies uh doing live streaming to energy uh companies like Palmetto all the way through.

Jenn GileAnd you told us uh that when you retired from your last company, um you decided to pick up maintaining as a hobby.

SPEAKER_00Yeah, yeah. So in 2013, my first startup uh got acquired, I think a couple of years before that, like 2011, uh by a company called CenturyLink. Um and so I was there for two years, and then I was like, okay, I'm gonna retire. Um found out that basically all my friends and uh basically work at the company that I retired from, and also they had jobs, and I have no other hobbies other than work. So I decided to give back and I was like, hey, I really like open source, and I actually started contributing to a couple open source projects.

SPEAKER_00Uh eventually I ended up uh taking over Ki V, uh, which is one of the ones that uh basically got the had the supply chain attack on it. And at the time it was probably, I don't know, about 40 million downloads or something like that. Since then, it's kind of grown quite a bit. And I think last uh estimate, it's like over 600 million downloads a month.

Jenn GileYeah, crazy. So let's rewind the clock to April or sorry, our August 4th. Um, and this sticks in my mind in particular because Paul and I had we just gotten to Las Vegas or were we just going? It was somewhere in there, we were headed for Hacker Summer Camp and we were like, cool. The the hackers know that uh the security industry is going to be at conferences all week. And so, of course, they picked this week to attack. And um, it kicked off, Jared, with you as the initial victim.

Jenn GileThey uh gained access to your publishing accounts, uh, published trojanized versions of several of your packages, and it resulted in an NPM worm that infected 444 packages. Um, the largest impact that we saw as we were analyzing it in real time was to an organization called Service Titan. Um but you know, we're gonna focus more on your experience rather than the malware itself.

Jenn GileUm I think listeners of this podcast know that Paul and I are team open source and uh would like to see a bit more understanding in the security industry of what open source maintainers go through, um, what it's like to be the victim of a supply chain attack and uh maybe give people some inspiration for what they could be doing better.

SPEAKER_00Yeah. Uh do you want me to just kind of start off with, you know, day the day of?

Jenn GileYeah, but first uh I think I didn't actually ask you this, so I'm gonna ask you now, what made you say yes to coming on this podcast and to talking to Paul and I in general?

SPEAKER_00Um, I think there's a couple things. Uh one, that I I was actually really surprised how much of the community actually reached out and has helped me along the way. And that that really changed my thoughts. I've always wanted to help people and contribute and things like that. But on the security aspect, I know nothing about security, like to be honest. And it's actually quite hard to actually get into security and understand what's going on. And I had so many people reach out and actually help me.

SPEAKER_00Uh, they were reaching out on Twitter, they were like, I had people actually get on a video call with me to kind of explain, like, and start looking at a couple things because I was like, I have no idea how this works. Um, and so after that, you know, I was talking with uh another person that I know that does open source, and I was like, you know what? I am, I'm gonna start giving back on this because like it's it's going to keep on happening, supply chain attacks. And a lot of the open source maintainers, they don't always maintain their code.

SPEAKER_00Like if you look across the NPM registries, part of the reason I ended up taking over a lot of these packages is because they just weren't being maintained. And it's hard to do that because it's free, right? And so a lot of maintainers are like, I don't get paid for this. I might get a$50, you know, donation once a year. And so that's why I started doing it.

Jenn GileYeah, I mean, people get burned out, you know, cycle off at it some point. We saw with the XC utils case a couple of years ago that that's how that package ended up getting taken over by a threat actor, was the maintainer was burned out. So I I don't know. I'm glad to hear that you had a good experience with the security community. Uh, we think the community is pretty special. So, you know, glad to bring this all together.

SPEAKER_00Yeah, and now it's like it would be even better. Like, so now I'm starting to reach out to other open source maintainers, and I'm like, hey, like you should start locking this down. If you need some help, let me know. Like, I'm happy to help.

Paul McCartyAmazing. I um I think I just wanted to say personally, thanks for coming on the show and thanks for being open to talking about this. You know, I cheekily wore my got malware shirt today, but I mean, I also want to be honest and say, listen, I get that August 4th and that whole week would have been one of the crappiest part in days or weeks of your life. And and I and I don't want to be flippant about that, right? That's oh yeah, I have done a lot of incident response with open source maintainers and with with software engineering teams, and I get that it's a terrible thing to go through.

Paul McCartyAnd so I don't want you to think that I'm being flippant about that. Um, so I I just personally want to say thank you for coming on the show.

SPEAKER_00Oh, no problem, and be as flippant as you want, because at the end of the day, you kind of just have to laugh about it because you go through something like that, and it really changes like how how you think about things and what you're doing. I know before we were even talking about like trusting people who reach out to you. Like, I used to always trust people, no problem. And I'm like, I don't know if you're actually the person that you're you say you are, which is I'm from Detroit.

Paul McCartyI'm from Detroit, I don't trust anybody. I don't trust nobody.

Jenn GileWell, why don't we start with like August 4th? How did your day start? How did this, you know, how did you find out you were compromised? What was it like? What did you go through?

SPEAKER_00Yeah, so um I usually go to sleep pretty late. Uh I'll start August 3rd because most likely that's when it happened. So August 3rd, uh I was working on my desktop, and just to let everybody know, quick background on it. I I have a desktop and a laptop that I usually work out of, and I'm constantly working. My desktop was uh compromised on that desktop, just like every other developer, you have a lot of stuff over time that accumulates, right? And I've had this desktop for five plus years, so it had secrets on it, it had ENV files, it had um, you know, what GitHub PATs, uh, and that's actually how it happened.

SPEAKER_00So we we could not figure out, and I've asked many security experts like, how did this happen? Like, was it a you know piece of malware that got installed? Because I think something happened like that, uh, but a lot of them delete themselves and things like that, or was it a phishing thing? Nobody has been able to figure out how it got compromised, but they were like definitely sure that this desktop got compromised. So that was the night before. Then by the morning, which I usually get up around seven, seven o'clock, eight o'clock, I had probably over 140 text messages, uh, 40 to 50 insta, like or Twitter messages.

SPEAKER_00And I literally like was downstairs pouring coffee and I just freaked out because everybody was like, call me, call me, call me. Like, literally, you've been hacked. And of course, I came up to my desktop, which was the compromise machine. I log on, I and I couldn't even see my GitHub account. Like it literally was like pushing, trying to, you know, I think they were trying to take it down. Uh, and it was basically like I had no access to GitHub, I couldn't even figure out what was going on.

SPEAKER_00Um, I went to NPM, no access on NPM. And then I started looking on Twitter and like literally, like everybody was like, it basically my entire feed was full of this.

Jenn GileYeah, we saw your um messages while like during the incident itself, kind of trying to get access back to your accounts so that you could, you know, incident respond, take down packages. Um, so what can you tell us about the experience of trying to regain control of your your maintaining accounts? I mean, again, we said at the top of the episode, it's not just key and cashable, you know, your accounts have access to possibly, you know, yeah, billions of downloads a week kind of thing.

SPEAKER_00Yeah, yeah. Uh it it was actually quite scary because a lot of the people that I I personally know who have been like uh Charlie Robbins, he was like one of the first people for know.js, right? He was one of the founding members. He reached out, we've known each other for a long time, and he said, You might never get your account back. And I was like, that's 10 years of work, plus like you know, corporate work and things like that. So it was quite scary to kind of figure it out. And I ended up, luckily, like I knew a lot of people at Microsoft and at GitHub, and I was reaching out to them and being like, I need you guys to help me.

SPEAKER_00And one of the things you probably saw posted is I offered like$5,000 to talk to a security expert, and uh no one basically would respond. So all I could do is just apologize on Twitter and wait for them to slowly engage with me. And the only way they engage, which is really scary, honestly, is through email. Yeah.

Jenn GileGiven how things got compromised, I mean we know your NPM and GitHub accounts were compromised. For all you know, for all they know, they could have been talking to the threat actor through your email.

SPEAKER_00Exactly. Yeah, it and it's kind of crazy. Like I couldn't get any responses from them, and I didn't know if they were working on it or what was going on. So I was kind of clueless. And luckily, the security community was able to like reach out to a couple of people they knew still at like NPM or GitHub and be like, hey, you know, how can we help? Um, eventually that got to the point that they started responding to emails and being like, hey, we're gonna activate your accounts, but you need to like do a couple things and start cleaning up.

Jenn GileBut it was so did they take down the malware or did you take down the malware?

SPEAKER_00So they took down uh so so and uh to their credit, like NPM uh took down the malware uh so would would stop publishing, which was awesome of them. And they went in and basically like removed all my uh OIDC publishing, which if you've noticed the improvements that they've done since then had actually been pretty remarkable. At the time, I thought I was doing all the best practices, right? I was being secure.

SPEAKER_00I actually were moved was moving all my packages to trusted publishing. Uh, but they didn't have at the time when I started moving it, which I think was like three months before the August event, it basically was like trusted publishing to fully publish. They didn't have staged packages or anything like that, right? A lot of those best practices just barely started coming out and rolling out for people. And a lot, so all the person had to do, or whoever hacked me, is I had one GitHub PAT that was really old and it was still being used by a small application that I had.

SPEAKER_00And it was back in the day when PATs didn't have limited access controls. And all I was doing was reading my repos. That that's what the app was doing. It would read my repos and uh do some work for me. But that one PAT that was on my desktop, that's what they pulled and had access to everything. And so once they had access to that, they they literally were able to change uh some of the settings and start publishing. So they didn't even access npm my accounts on there.

SPEAKER_00They were able to just fully publish right from GitHub.

Paul McCartyThis is really, really fascinating and interesting to me because this has this has connections to other things that Jen and I deal with all the time right now. Um so I I want to double click on the npm and the GitHub account. So you you know, you you saw that did you see that the bad guys were trying to push something to GitHub, or you just noticed that I can't do anything to GitHub because it's down, my account is effectively deleted.

SPEAKER_00Yeah, so at the time I saw another, like they were trying to push another release. So you saw them like trying to bump it and actually push another release. So they already had one. I think it was like earlier in the morning, right? I think it was like 3 a.m. when the first one went out, or 3 a.m. my time. Um, and then what by the time I got up and I'm panicking, like I couldn't log into any of my accounts or anything like that. And you could see basically the CI CD pipeline still trying to do a release.

SPEAKER_00And they even moved to another package of mine, which is much smaller, um, called Ecto. And they were trying to publish through there also. Uh, but just by doing Ki V, which is you know about 600 million downloads, cachable is a whole bunch of caching libraries that Ki V basically is the back end storage adapter for. And that's like ESLint uses that, uh, GOT uses that. Um, it has a whole bunch of different caching libraries uh that I basically maintain and support.

SPEAKER_00And so by getting both of those out the door, that's what they were trying to do again. And it looks like GitHub uh security team really stepped in at that point and stopped all the jobs once they figured out what was going on.

Jenn GileSo the attacker presumably had changed your GitHub password, or were you did you still have access in any way?

SPEAKER_00Yeah, I couldn't log in. So I don't know if they changed it, most likely they did, or if GitHub basically uh just turned off the user and then eventually they took down the entire my entire personal account for a little bit.

Paul McCartyYeah, so I think that this getting back to this observation I had about how Jen and I see this, when we see that right now there's thousands of GitHub users that are being affected by like Pollen Rider or Ghost Action or just this new one that's happened over the last couple days called WFX. And the problem there is those people that have that bad stuff in their package, sorry, in their repos are victims. Now, the problem is when I when I tell GitHub about that, what they do is they actually delete that person's account.

Paul McCartyAnd I think, and this is kind of this is what happened to you. I mean, you got your account back.

SPEAKER_00I mean, it's scary, like that it could be deleted, right?

Paul McCarty100% because not only did you have all your repos, you had your connections to enterprises and organizations for your GitHub account. And here's the other thing is GitHub acts as an identity provider for all kinds of stuff. You can even use you can use GitHub as your identity provider to log into Microsoft, Microsoft Live and Microsoft 365. So I think uh the reason I wanted to kind of double click on this is just to say this default behavior, which I get it, so I think we get it at some level.

Paul McCartyLet's let's kill the user temporarily, so figure out what's going on, we can fix it and then we can re-enable. But this thing where they're like deleting accounts, you know, permanently in some cases now, that's very destructive because that user that might affect other things too as well.

SPEAKER_00Yeah, it and I actually had that experience uh because the first thing I was using a keto, I actually installed a keto security scanning on my PRs, and I wanted to see what they saw before it happened, and I couldn't log in because I used my GitHub access token. And that experience, I was like, I really have to change the way I think about this moving forward. Um, because you're right, like I you I was using it for identity everywhere, right?

SPEAKER_00And to have that access taken away was pretty crazy.

Paul McCartySo, Jen's side note, we use GitHub as our I know, I'm thinking about it.

SPEAKER_00Yeah, well, a lot of people do. I mean, it it's just so good to have that. And a lot of all developers have a GitHub account.

Jenn GileYeah, I mean, I think this goes back to something I talk about a lot when I'm trying to help people understand like GitHub started as one thing and it has become another thing. And in the time in between, it hasn't necessarily matured in ways to support that other thing. So, you know, we haven't even talked about GitHub as an IDP, but you know, this whole security um gap that's with it where massive amounts of malware can be uploaded and persist on GitHub for days, weeks, months, and the only real solution is to kill accounts.

Jenn GileThat's certainly not supporting what I would assume is GitHub, like probably does want to be your IDP. So there's gotta be some layer of like better trust, better account validation, like to your earlier point about uh the only way to talk to them was over email. Like that's concerning for a whole host of reasons. Never mind the whole account takeover part, but in the you know, need to validate who you are, to have quick communication.

Jenn GileUm Paul, I don't remember the last time I sent you an email. Like trying to communicate through email is not exactly a rapid, rapid route.

Paul McCartyYeah, and and I'm assuming that Jared was paying at least for a pro account, if not for enterprise and some of his accounts, right? Or at least he was connected to paying enterprise, right?

SPEAKER_00Yeah, I pay for the pro account.

Paul McCartyYeah, I mean, like I'm a paying customer, Jared's a paying customer, we're a paying customer, Jen. I this is part of my frustration with GitHub, and this is where I wanted to go with this next is you know, in your post mortem, you thanked GitHub and NPM security teams, which I thought was lovely. Um, I also wonder how helpful they really were. So I'd like to double-click on this here, like if if you're okay with that, and say, like, I mean, what were they really how were they helping in their emails and like how how responsive were they?

Paul McCartyUm, and by the way, too, um, your npm account also got killed temporarily. Is that correct? Or is it not?

SPEAKER_00Yeah, my npm account uh was taken down while they were do doing the cleanup and removing stuff. Um, so we'll we'll double click a little bit on this, and just to let everybody know, like I know a lot of people at Microsoft and GitHub. You know, I've I've been in the Seattle area for 25 years, right? Or over 25 years. And so I I thanked them because it's a lot of work to basically like clean up somebody's mess um and figure out what to do and build those policies.

SPEAKER_00I would probably say like the communication thing is the one thing that if I had the chance or opportunity, I would really want to help out with. Um, not you got to think about it. An incident like this where you're affecting hundreds, if not millions, of packages that can be affected, can be installed, secrets can basically be released. If you take my That update, like in your, you know, building out your Docker container, and you take that update, it's going to scan those secrets right away.

SPEAKER_00Right. And so that's the one thing, like communication-wise, I really wish I was, I would be able to call a number and get someone on the phone to just talk through it. Like, what do they want me to do? What's their plan? Like, how can I help? And from my understanding, the current policy is you can't do that as a security person at Microsoft. You can't basically like red team an incident with the person who's affected.

SPEAKER_00But that would have really helped because I would have known the next step that I needed to do instead of just wildly asking the entire community like, this is what's happening.

Jenn GileYeah, to your point, your projects have such an enormous blast radius. It's not just the download statistics, but also they're used as a transitive dependency in tons of projects. You know, I wouldn't necessarily expect Microsoft or GitHub to help everyone, you know, directly over the phone. But for a compromise of this scale, I would want to see more.

SPEAKER_00Yeah. And by the way, like, you know, we've talked about this before. I offered$5,000 to talk to a security expert, like any donation. At this point, like, and I've floated it to other people at Microsoft. I was like, look, if I could talk to the person who's over that policy and a security person for one hour about just changing it, I'm happy to give$50,000 to any donation. Like, I'm serious about it. Because like it is so critical that you have to like get everybody in the room to solve a problem.

SPEAKER_00And I've been CTO for many companies. It is really hard to have a security incident without everybody in the room figuring something out.

Paul McCartyI feel like GitHub, when Microsoft bought GitHub, they had the strategy for why they did it in 2018. And I think they didn't realize that they were buying plutonium, which is great if you know how to use plutonium.

SPEAKER_03Yeah.

Paul McCartyBut if you don't know how to use plutonium, it's radioactive and it will kill you. And I think that that's kind of where Microsoft is. And I and I want to briefly before we move on, because I know Jen wants to uh we both want to move on, get to the more cool stuff. But I think Amazon, for example, you can pay them for support. And even if you don't pay them for support, there's an ability to quickly escalate. And listen, I'm not saying Amazon's amazing, but I'm saying Microsoft, Amazon. They're both really big companies, they both have a lot of money. One's doing a good job here, and one's doing just a really, really poor job of addressing this.

Paul McCartyAnd I would make the argument that the stuff that happens in GitHub has, to your point earlier, has a larger kind of attack, you know, structure. Sorry, not attack structure, it has a has a bigger impact, sorry, uh uh, you know, internationally and globally than perhaps somebody's Amazon account does. So there's that too.

SPEAKER_00Yeah. I mean, here's a great example. Like I have been using GitHub for a really long time. When I got my repos back, I did not realize that they still had the uh branches with the malware on them.

Jenn GileAnd I didn't know what my next didn't tell you that they didn't clean them out.

SPEAKER_00You could have I mean they're like, hey, we're gonna restore your access, you know. And I remember I'm I'm using like two-factor authentication MFAs for like I've been doing that for a long time. So it's like, okay, we can restore access, but luckily I had a couple of people on this like in the security ecosystem that's like, hey, just let you know you got to figure out how to clean this. And then I'm like, how do I actually clean this? Like, I'm not a GitHub or a Git expert, right?

SPEAKER_00I use it for revision tracking, but I'm not that right. So I had to research basically for about two to four hours to figure out how to clean this properly without infecting myself or anybody else. And I was still getting pinged by the like everybody out there being like, you're still infected.

Paul McCartyWell, and and you're probably worried at this point, is GitHub going to take me down again and like break this whole thing? I'm like, I'm 80% of the way to like addressing it, and now you take away my access again. Yeah. Um, I I think that's a great point, too, as well, which is GitHub chose to build their platform on top of Git, which was was written a long time ago in what I describe as a time before security, and it doesn't have any security built into it. There's no authentication, there's no authorization, nothing. Yeah, and a lot of these fixes to your point have to happen in the Git repo and in the Git branches and in the index itself, not in GitHub.

Paul McCartySo they just handed you the plutonium right back. They're like, Oh, here's your account here, and you're like, Oh, what am I gonna do this?

SPEAKER_00I I honestly was I want to thank everybody again because people were like, You just it's back online, do not download and run anything. You got to figure out how to clean these because it's still infected. I was like, How is it infected? Like, I didn't even know how it was infected.

Jenn GileSo, how did you figure it out? Was this you know, diving down Reddit holes or Stack Overflow? Or how did you how did you teach yourself?

SPEAKER_00I mean, that so after that incident and I got back my repos, the first thing I did is disable all publishing. I went through every single one of my packages, all my GitHub actions, I deleted all the actions. Like basically I went to So the workflow files themselves. Yeah, I well, I just well, not the files, but like you just disabled a runner, I disabled every single one of those, all my publishing, all my OIDCs. I went through every single package and got rid of them. I was like, okay, we're just not gonna publish for a while, right?

SPEAKER_00And I have a lot of repos. So like usually I'm publishing multiple times a week, things like that. And then I basically uh it's kind of funny because my family was heading to the beach that day. So uh luckily, my uh they I was supposed to actually drive and pick up someone in Portland and then uh head to Manzanita. So they all left, and uh my brother-in-law came and picked me up after the incident was over. And basically, I was on my phone, like basically talking to people about like, okay, what should be the next steps?

SPEAKER_00And this is how I ended up with this whole defense in depth.

Jenn GileUh yeah, walk us through what you sent me to take a look at, you know, a couple of months ago. What you've written, I don't want to call it a manifesto because I feel like manifestos are not actually practical, it's just like a rant on a piece of paper. You built, you know, an architecture for yourself that you've been, you know, using and tweaking and writing about and telling other maintainers about. So, how did you approach that? Because, like you said, you didn't have a background in security, secure coding, other than I'm gonna use all the widgets that GitHub has here.

SPEAKER_00I mean, yeah, and that yeah. So I was talking on the phone for basically like four hours calling friends, people who I thought were more secure. I talked to uh security experts. And one thing that I learned in that four-hour drive is everybody has a different opinion, and no one can tell me how to lock down what what the best practice is to lock down an entire flow. So, like, how do you lock down your desktop and create isolation and reduce your attack surface?

SPEAKER_00Most people just have opinions. They're like, you should try this. What's it gonna work? Especially for someone that's you know needs a really good developer experience. Like, there's days that I do a hundred, almost 200 pull requests in one day. Like, I can't just be like, oh, I'm gonna spin up like a brand new parallels desktop, wait two minutes to basically pull down some code. Like, you got to figure out how to rapidly do it. But after those four hours, I was like, okay, no one knows like really the they're like, here's a best practice to lock down GitHub.

SPEAKER_00Here's how NPM staging should work. Here's a tool that you should look at. Here's this other tool that you should look at that does something similar but a little bit different and is not really maintained. But we all like it. Here's a a scanner that you should look at. And so basically, I decided that I was going to maybe we can call it a manifesto, but I was gonna build an agent skill that basically does full defense in depth. Because after thinking about it, I was like, this is gonna take me three to four months if I did this manually to lock down everything and set all the right permissions and you know, even even GitHub.

SPEAKER_00I couldn't figure out how to lock down certain things in GitHub because it's so complex, right, over time. Like, how do you require certain runners to run? How do you make it so that nobody can add a runner by accident? How do you scan the code? How do you you know have release gates? I didn't know any of that. And honestly, I didn't have that type of stuff. And so I basically spent, instead of being like, I'm gonna lock down everything, I got to the beach, I figured out how to clean the repos so the malware wasn't there, which took me about six, seven hours to figure that out and do it properly in an isolated environment.

SPEAKER_00I spun up basically um a Parallels desktop and basically ran the commands working with uh ChatGPT and Fable to tell me what to do right. Because it it was actually kind of scary. Like I was double checking those git commands because it's basically you're deleting like branches.

Jenn GileRight. You want to be extra sure.

SPEAKER_00Yeah. And then I once I got that done, I was like, okay, I'm gonna spend the next couple days really figuring out how this needs to work. And I had to try things out, right? Like I first was like the first recommended was use uh uh local containers, right? Like uh spin up local containers and use Visual Studio Code uh with those containers, and they're all isolated and just delete them after every pull request. And I actually tried that, and I was like, this is a horrible developer experience.

SPEAKER_00It's really, really hard to do because you're you're constantly just churning on those containers. And then I started realizing like I'm gonna change it a lot more. Uh, there were two truths, and I actually blogged about this that I realized I was gonna have to do. One is in the age of AI, most likely a lot of my code is gonna be written by AI. And the second one is I need to be in isolated environments for almost every pull request. And so that's how I started building it out.

SPEAKER_00So I took those fundamental values and I was like, okay, where is gonna be the attack service? Where's gonna be the bottleneck moving forward by moving to isolated environments, to configuring things correctly? And it's literally this checkbox that I run on every single repo. And it's uh it's a really good skill. So it locks down all of GitHub now. GitHub is basically my release gate system. That's probably the biggest attack surface at this point. But all AI, all coding is done in isolated, isolated environments.

SPEAKER_00Uh, usually they're they only run once and then they get deleted. Uh only time that's a little bit different is code spaces from GitHub. So uh, and that basically only lasts, I think, seven days before it gets deleted. Um so that's kind of what I did.

Jenn GileAnd it took Yeah, you said that you've one of the components is an agent that's like your security manager. Uh talk us through like how did you decide for that agent to, you know, what was it gonna do? How did you uh make sure it had the right context given you're not a security manager? How did you, you know, teach it to be the thing that you're not?

SPEAKER_00Yeah, so uh to give you an idea, I once I got defense in depth done and I started applying it to smaller repos, I was learning a lot as I was going on what needs to be there and what doesn't need to be there for AI to actually apply those features, even to the point there's actually a script called lockdown uh that's a.sh file and it basically like you log in via terminal to get uh gh, your GitHub CLI, and then you run the lockdown on a specific repo, and it kind of figured out how to lock everything down.

SPEAKER_00Because I honestly couldn't figure out how to find everything in GitHub to lock down. Like if you needed to do this again, yeah, there's no way I had AI write the script for me that I could run it over and over again. Um but getting back to this, like what I ended up doing is after I got all the repos basically with the the full defense and depth, and it can validate it, I was like, okay, what's the next step? And the next step is constant looping on it because I'm gonna I know I'm gonna improve defense and depth.

SPEAKER_00And I've already, it's probably gone through like three or four iterations. And I I've even had some people be like, hey, we really like what you've done with dependency management skill that you have, which I run every single month uh on on my repos to basically update the packages and things like that. But they're like, Can you do it for other ecosystems, like Python, Go, stuff like that? So I'm already working on that for defense in depth, basically having another project to maintain. Yeah. So I was like, how do I loop this?

SPEAKER_00How do I basically because the security stuff is coming much faster now? Like, wasn't it two weeks ago that like we had like four zero days and like a 72-hour window?

Jenn GileBad week.

SPEAKER_00Yeah, yeah, bad week. But that's going to keep on going. So I decided the better thing to do is to have a bot that is my director of security. And what it does is it actually looks at a couple sources. Uh I can't remember whether, but anyway, looks at the sources, also looks at Twitter, and then it's like, hey, if something posts, I basically had to train it to verify it, validate it, and then look at all my repos and see if I'm affected.

SPEAKER_00And if it does, it automatically opens up a PR for me to actually uh look at. Because I want that loop always going. The other thing it does is it makes sure that defense in depth is actually still on my repos. So it checks that every single day, uh, usually every two hours, it's checking all my repos and things like that. And then the final thing is the dependency management skill that I have. Now it runs every single month and it picks up the changes for defense in depth.

SPEAKER_00So all I have to do is update that one skill with a change that I really want. And then next time I run dependency management, it's now updating with defense in depth.

Paul McCartyI I think there's like there's so much that I like about this, but at the same time, my security hat is like, because I've gone through a very similar process, Jared. Like I, you know, I moved to like isolated environments for for uh coding. But then the problem is that you have to, and we were talking about this before we went live. You know, you have to you have to seed that environment with access to GitHub to be able to get things, especially these are private uh repos. And that means using the GitHub CLI or using paths or using some other way to give that machine or that instantiate instantiation access to those things, but then even worse, you have to allow it to then write and like the GitHub CLI cannot do pushes, right?

Paul McCartyIt can clone, but it can't push. So that means that you need to, if you're using SSH keys or if you're using you know GPG signing and all these things, you have to get all that into that environment, orchestrate it and and make it work, and do that again and again and again. And it's hard, it is genuinely difficult. I oh I struggle with it. Yeah, I mean, I struggle with it personally, and I've been doing this a long, long, long time, and that is very um it just reminds me how difficult this is for developers that haven't had 30 years of security experience to do it as well.

Paul McCartyAnd so, so everybody listening, Jared asked me the other day. He asked me very poignantly, he's like, What can I do to make and I was like, sorry, mate, there is not one thing. This is like, you know, I can't tell you to put your seatbelt on, or the abs brakes are gonna fix you, or the sensors, right? Like it's all of it together and a bunch of other stuff that we have to constantly be iterating on. And so, like you, Jared, I think it's about you know putting stuff in place and then iterating on it and testing it, and not assuming that you've solved the problem and moving on.

Paul McCartyYeah, I don't think it's all it's not. Uh the attack that we're seeing right now in GitHub. I showed it to a friend of mine and he went and took a look, and he's like, Oh, all they're doing is writing markdown. And I'm like, No, mate, if you call the GitHub API, you'll see that they wrote markdown, then they pushed an action, the action ran, they did all these things, and they deleted it all, and all you can see that's left over is one line in a markdown file. You missed the point. They just looked at it and thought, oh, there's nothing going on there, right? The reality is that a lot of bad things went on there, and you just didn't understand that you had to go and look at the event API to get that data.

Paul McCartyYeah. Um, and I we were talking about CLI, sorry.

SPEAKER_00I I agree. Like it is also crazy, like the even the SSH, because you need a good developer experience. And sometimes what like there's things I there's things in my attack surface that like I'm still trying to figure out. Like, for instance, what you were talking about, you have to give it access to GitHub, usually through OAuth, right? If you try and do a PAT or something like that, it gets really cumbersome when you have this many repos going and this many agents, right? Like SSH is a great example.

SPEAKER_00Everybody was like, hey, you should start signing your code. And so I dug into that for a week, trying to figure out how I can use agents, provide, do SSH signing, and sign my code and still have it published pretty seamlessly. I could not get it working.

SPEAKER_03Yeah.

SPEAKER_00Without like a huge amount of hassle, like waiting for an agent to ask for a prompt so I can give it an SSH signing envelope, and then it's still on that desktop. And then sometimes it would mess up trying to push something. It was a nightmare. So I can't do SSH signing.

Paul McCartySo that's why when you go and look at people's git history in in a particular repo in a particular project, you'll see they've signed a commit because they did it themselves manually, but then the next one, which is pushed by Claude or their agent, it's not verified. Yeah, because it's really painful. And I wish these were things, you know, going back to the GitHub CLI, the GitHub CLI is a particularly pernicious problem. Well, look at my alliteration. I'm crushing it today. My kids would be so impressed.

Paul McCartyUm, didn't even plan that. Uh but you know, it there's no there's no MFA, there's no two-factor built into it. It saves your credentials in the config file in clear text. A lot of people don't realize that, regardless of whether you told me. Yeah. And it even it so if you hand GitHub a pat, it's gonna store the pat in the config directory in clear text. If you auth in overall, like it's gonna save that session, which is the ghsa underscore s in that same directory in clear text. Come on, GitHub.

Paul McCartyLike millions of people are empowering their their agents with the GitHub CLI. I mean, it is the default behavior now is to use the GitHub CLI. If it sees that it's authenticated, it often doesn't even ask if you're in auto mode. It just says, Oh, sweet, the the GitHub CLI is installed, and I got an off status. Yes, let me go ahead and use it. We need to be addressing these things individually. And I think there's only so much that you and I, Jared, can do. And honestly, getting back to Paul Kick and GitHub, they need to do more with a lot of these tools that they put out there.

Paul McCartyThey need to be doing more.

SPEAKER_00Yeah, yeah, I I think they're trying to do the best they can. And to be honest, once I learned about some of the security stuff that you can do, especially that that they've added probably over the last five plus years, like branch you uh rule sets on branches, like that's an amazing achievement to add that in. Like, that's really great. Uh, and but I could not figure out myself how to actually set this up without making it really painful, right? I didn't even know about a code owner's file.

SPEAKER_00Like, none of these best practices, like, why would a developer even look that up? They're they're trying to ship as fast as possible, especially in the these days, this day and age. And it was really hard to figure things out and be like, like you get a suggestion, hey, you need to add a code owner's file and lock down certain things that need basically like someone to actually look at and approve.

Jenn GileYeah, it might I mean I would be interested to hear about your list of things that you thought would be easy that were hard. Because as we were talking about as we were prepping, there's definitely a lot of narrative when a developer gets compromised. Well, why didn't you have code signing turned on, or why didn't you have this? Or, you know, as we were you know talking about uh you know should we just stop uh using open source and you know maintain all that code in-house uh these are all things that are easier said than done but they're also like particularly pernicious myths.

Jenn GileSorry, I couldn't come up with a third P. PPM I I worked on it. It didn't go far. But there there are these narratives that float around the security community that I also do hear from developers of, oh well, this feature is there. You know, this wouldn't be a problem if you just turned it on. So I'm hearing you say code signing, not as easy as it sounds.

SPEAKER_00Still can't get it to work. What else? Uh so code signing was one of them. I was like, this is actually way harder, especially in the age of AI, because things have shifted, right? It's not if if I had a local desktop always running, I could have that key always there, right? But you don't want to give AI that key. And so how do you publish, right? It's it's hard that way. So code signing was one of them. Uh branch rule sets, when you go into that UI, like it is actually really hard to understand what you should and should not turn on or off.

SPEAKER_00And it it is not descriptive in any way for someone like me. Like I had to go through like every single one. At one point I took a screenshot and I told Claude to describe what each feature did and how it would change things.

Jenn GileAnd was it able to find documentation for those features?

SPEAKER_00Yeah yeah but even the document is really confusing. Like it is it is written by a security expert without like hey a common developer should have these default things set. Like it is really hard to do. So I had to go through almost every single one of them and be like okay if I turn this on and turn this off and this is off what would happen? And I had to do it for every single one on the rule set page.

SPEAKER_00I did it for uh a lot of the security settings uh one thing I I turned on and instantly turned off is dependabot it was horrible like I can't manage it because was it just too noisy or was it super noisy and it would basically kept keep on popping popping up like alerts but you go into the alerts and to be honest like those CDE alerts are unbelievably hard for a developer like me to figure out like do I need to care or do I not well and also too like like let's just assume that what Dependabot is telling you is legit.

Paul McCartyIt is difficult in many of these cases to actually do the thing that Dependabot says because it immediately you test it on your own machine and it breaks the app that's because that's because it's now using the new version of Kevin or whatever you know whatever the case may be like this this overly simplistic idea that and this is another one of those InfoSec myths right with people InfoSec people me like people like me yeah you know who never came to the software engineering space to understand how it works saying these simplistic things like we'll just upgrade to the newest version of that I'm sorry mate that doesn't it that doesn't work you know 80% of the time or whatever because of n reasons right yeah and that that's one of the things I had to do with my uh director of security like basically like when it finds something and it needs to do an override luckily like I have end-to-end testing in GitHub actions but it also like has to verify everything.

Paul McCartyIf it's breaking I tell it to upgrade the model and figure out what all the changes have to be dependabot is the single most useless feature they have ever pushed because people think it's a it's really noisy.

SPEAKER_00I I ended up by default turning it off and people are like well you're not secure and I was like well I also have like security scanners running on every PR. I do regular dependency management which a lot of people don't do. The other thing that like was actually it took me a while to figure out is how to lock down containers and add things like you know a a scanner like you know a security scanner I had to look at a whole bunch of them that like PMG got recommended and I really like that project because they're moving in a direction that I I like I ended up with a keto's supply uh their akido shim um to set that yeah to set that up I had to figure out like oh I need a a dot dev container folder and what is the config for that and how do I verify that it is always there how do I tell an agent that they can't run anything until everything's installed right yeah so to I think what you're saying is another thing to add to that sounds easier than it really is list is turning on code scanning of some kind.

SPEAKER_00Yeah I mean these are like two to three hours of discovery that you have to do as a non-security expert for every single little piece of flow. The last one which took me the longest is how to basically do release gating in GitHub actions. And I like scan things beforehand before you publish it and what is a staged publish on npm now because it's a new technology and you know how do we verify that that staged publish is really good well you have to use something like dry doc or something like that.

SPEAKER_00And it's really interesting going through that process adding all these tools and then trying to make them actually work together.

Paul McCartyAnd if you're if you're whatever it is that's trying to ascertain whether or not that staged thing is good or not has to have to sorry has to have access to npm to be able to see it because if you're looking from the outside that staged artifact has nothing in it's a package on a and a readme and that's it right so you need to have so you have the same problem. When you're building these Docker containers right to do it all the right way you have to get your code in there and you have to get your code in there in the in a way that's not gonna you know blow up inside the container now because you gave it access to the code and gave it the ability to do things that you needed.

SPEAKER_00Yeah and I made a policy that um and uh even on my blog because a lot of people ask like why is my desktop set up now I use very little um apps anymore on my desktop like I have like my calendar my password manager uh you know my music app but pretty much like I do not install other than Visual Studio code which I do not install any plugins except for the AI that I'm using which is usually uh codecs for that but that's running in a dev container also that's the only dev app that I'm running because to be honest like cursor uh claude desktop uh even chat GPT desktop I don't trust them anymore because I think that's going to be the next attack vector so I run them all in a browser.

Paul McCartyThat attack we deal with that attack vector all the time right and it's really hard when you open up your VS code or your cursor to understand what plugins and extensions are already there existing when you open it up right yeah yeah so I had to move away from that and it's kind of crazy.

SPEAKER_00So you people like us in across all open source like we're gonna have to really think about this. And I think a lot of developers are going to have to really think about the entire process what happens at your desktop what happens in the cloud what happens when a pull request lands what happens when you're ready to publish what that looks like like I did not know that you could actually set releases well actually one of my friends told me he was like hey he was reviewing the defense in depth and he goes hey by the way you should make your published releases non-editable and I was like I didn't even know GitHub had that feature.

Paul McCartyAll right I have like there's so many other things I want to say here but I like I want to I'm looking at time being I have one last question that I want to talk through that I feel like is a little bit of a wrap up um we're all still team open source in this room right now.

Jenn GileSo presumably like you're still in circumstances where you need to use a new project from time to time or your agent suggests it. So like how do you decide whether you're going to bring a new project in outside of you know does this thing do the thing that I need it to do?

SPEAKER_00You know how do you decide this is not going to increase your attack surface unnecessarily yeah uh I've been having a lot of conversations with other developers around this some people have said hey like open source is going to be dead I know people have mentioned that I think that's actually the wrong approach um just because a lot of these have a lot of eyes on these projects and usually if they're being maintained well they're they're actually having a lot better security fixes and best practices.

SPEAKER_00When I look at dependency management um I usually try to keep it as little as dependency uh you know chain or tree as as possible especially uh with Node.js but when I'm looking at like something an AI is recommending to bring in I I actually have a skill that I run on that uh that specific one and it checks a couple big things one it checks how often do they publish is it basically being actively maintained on the publisher I now I'm checking if they actually are doing OIDC if it's more modern uh I also check how many dependencies it actually brings in and if it's like over like 20 or 30 I start really considering like do I not want it?

SPEAKER_00And then the final thing is it actually goes out to the GitHub repo where that is and sees how many contributors have been contributing to it. When was the last updates are they actually doing security stuff and then it does a quick code review of their process and then it basically it gives me a score high medium low like should I do it should I not and there's been many times now that I actually decide not to bring in a dependency and have just for that one feature have basically like AI coded.

Jenn GileI'm curious as you're looking at activity this is something Paul and I talk about a lot because we see it faked a lot are you looking at the activity in the web portal or are you pulling um like the git history?

SPEAKER_00It's pulling the git history but when I talk about um so it does pull the git history because I I know in the like the web portal it's a little bit interesting. The activity that I'm more interested in is the pull request comments. I want to know if people are actually actively engaging and understanding what's going on as maintainers. And to be honest like a lot of open source and we've talked about this before the show it's really hard for maintainers to actually maintain because it's free, right?

SPEAKER_00It's not their day job. It's really hard to you know keep up on things.

Jenn GileUm so yeah yeah that's a really interesting signal to look for actual engagement rather than just healing as code shipping.

Paul McCartyYeah there's a there's a project from the open SSF called scorecard which I actually have done some open source work on myself which does a lot of that as a project and um so if if if you're not familiar with Jedi because there might be some things there that you can steal or just start using scorecard in parallel to your own stuff. But are you at the same in that skill are you also checking open source malware to see if if any of those packages are are malicious yeah I do. Cool that's super cool. But I can we're like it's I it's hard to detect that stuff it is it is especially when we start talking about those transient dependencies to our pro earlier right what's in the package manifest that's one thing.

Paul McCartyBut when you start looking when you start taking a look at the at the the lock file or trying to figure out yourself in real time you know what what the the the actual dependency structure is and I think also like in the open source world I think it's a very long tail of packages but most of the time people especially AI they're gonna choose the bigger more popular packages uh they're more maintained just because they've been trained on that it's been used more and I think that's gonna continue.

SPEAKER_00And people are you know it used to be like every little thing that what you needed there was a package for and I don't think that's going to be the end state of open source. I think it's gonna be a lot bigger roll-up packages that do a lot more stuff.

Jenn GileYeah you know it may be that direction for the packages but we're seeing the other direction for uh skills and um other agent focused things there's yeah MCP servers you know we're seeing a boom of that on GitHub many of it is malicious and designed agent rate and uh there's um some really good research from a company called island security that they did over the summer where they showed and I was able to recreate it asking your uh agent for a recommendation and it's serving up malicious uh repositories.

Jenn GileSo I was able to get it do that. It gave me a malicious MCP server that was pretending to be for Walmart.

Paul McCartyIt's called agent for baiting that's amazing.

SPEAKER_00It is I mean I've heard of that before I I want to I want to ask the GitHub actions question.

Paul McCartyI know we're going long now but I don't care um when we talked last week Jared you said at the end of this whole thing and I thought when I heard this I was just I was really amazed and I was struck by your optimism too as well which I think is really cool. You said after all this happened it made me really want to understand what GitHub actions does and really focus and really centralize everything I do inside of GitHub Actions. And at the time you know me you know the way my brain thinks I'm thinking I want to run as far away from GitHub actions as possible.

Paul McCartyI want to get away from it as quickly as possible. And here's this guy that's just gone through this compromise that has happened in GitHub Actions and he wants to do exactly the opposite. So first I commend you on sticking around and wanting to make the neighborhood better. But I guess kind of can you talk to like what your thinking is like what your thinking was about why you really wanted to do that.

SPEAKER_00Yeah I mean I I first started being like maybe I shouldn't use GitHub actions anymore. That was actually my first you know when I really started getting down to like basic principles I was like this could and I know that that you have to like do GitHub actions a certain way to really secure them and lock them down. And it's an old technology I mean it's a YAML file like it's kind of crazy that we think that way. So I actually spent about a week trying out other CI C D platforms and trying to see like how it all flows together and how you you know still use GitHub or use something else and then use a CI C D I really tried to open my mind up to like how am I going to do this just like I did with my desktop.

SPEAKER_00And what I basically realized is if you want a really good developer flow, you basically have to go all in on something to get it to work correctly because when you try to add all these like currently and I do think in the future that will not be the case I think CI there there's a lot of work going on and I saw the potential there's a lot of companies starting up that are like really fast CI C D understand agents.

SPEAKER_00This is an old school technology that was built for humans and slow code reviews and so I tried a lot of those but they weren't mature enough to actually have the flow end to end. Like a lot of them you can't do OIDC publishing to NPM so I was like oh well maybe I'll just have that one action and then like all the tests on something else. But then I started digging in I was like well now I have to have a defense in depth for them which is another attack surface and basically GitHub also.

SPEAKER_00And so you're getting down to this point where you're like always saying now I'm opening up this attack surface because what if they get hacked and how do I know and these are newer companies right building these out. So then I was like okay well I still have to figure out how to lock down actions right and secure those and get those working. So I kind of just went all in at that point. So that's kind of how I went to that I do think it's an old school technology. I I think they're gonna improve it over time.

Jenn GileBut I mean I've said this probably on repeat the last two years it's gonna be an interesting 12 to 18 months. Yeah let's see where this technology goes maybe if we talk to you in a year you will be totally off GitHub.

SPEAKER_00Yeah and by the way I even uh I looked at Origin right from cursor and I was like oh this is actually really cool but then you start having things fall apart and I agree with you like it could be like you don't have to be on GitHub anymore. And there's a lot of development going on for that and I'm excited about it. But it doesn't work end to end yet. And that's what I need to go fast or faster right to keep that developer experience going.

Jenn GileYeah as a maintainer who's doing this as uh you know a way to give back and not a full-time job you don't have a platform person on staff and a security person on staff to be able to make sure these things are strung together right yeah I I think honestly like so I've been CTO for a lot of companies to really lock things down you need almost like an entire DevOps security team it can't be just even one person anymore because it's so many different variances.

Jenn GileI think a lot of security people uh will be really happy to hear you say that we've definitely seen a lot of jobs go away because of uh the perception that AI can do it better faster stronger app app sec teams particularly in the last two years have really been hard hit is unfortunate that's interesting assumption the assumption is that AI would do it for us which I think is ridiculous.

Paul McCartyI I also think to your point I think you need eight you need a team players too you need top tier players right like you like you can't if you're if your app sec person is just doing vulnerability management which by the way a lot of app sec people are just stuck doing vulnerability management and vulnerability triage right let's just be honest right they're not really doing app sec they're just managing whatever it is your vulnerability engine is right so that you know you need top tier players to be able to really kind of tackle this stuff and be looking ahead to see kind of like threat modeling you know where are things going to go right to your point earlier about how AI is changing there's a speed and the pace and the fact that you've got a bunch of different agents working on the exact same piece of code and you have to like kind of figure out how to kind of bring this back together into a unified code base and do that securely that is really difficult to do at velocity.

Paul McCartyYeah we live in the we live in the cult of speed right speed is is most important above all things else which I think is a problem but in that cult of speed then the problem is you have to be able to do these secure things at that line speed and that's just I mean it's basically impossible to do.

SPEAKER_00Yeah and I like that you said a players because you know I would probably say I've had this problem in the past working with security teams to be honest like most many non-A players and maybe it's a skill that like we need to really focus on and I I'll say this also for uh uh SREs or DevOps engineers they're so nerded out by like what they're doing in security or infrastructure management or anything like that they forget the fact that who their customer is is actually the people trying to produce something right for the company.

SPEAKER_00And they either make it the developer experience so painful that nobody actually ever wants to work there. Like you know locking down their desktop actually this is really funny at CenturyLink we we were a cloud computing company that they bought right so we had data centers we had you know all of our engineers had access through VPN to their infrastructure because if you build it you ran it. And I remember the first day or week after we got acquired they uh gave us a new internet that had no access to VPN so we couldn't actually get to our infrastructure told us we could only do that then they sent us new Mac laptops and they were so locked down that an engineer remember an engineer making 250K a year would have to call the uh help desk to get Visual Studio installed and the help desk person would do the install I was like antiquated yeah and and you're like yeah it's improved over time but like you got you got to figure out how to help people like where they're at and make it still go fast or make it so they can produce yeah you got to make the right thing easy.

Paul McCartyI mean enterprises building these like lockdown golden image windows images for company for for the developers I just recently I'm not gonna say who is but I recently did anyhow and I just the limitations in that their engineers they basically can't use any agents at all except Microsoft Copilot and like just the limitations I'm like how can they perform at their top peak and then that's the thing then is that you can't expect them to operate at peak speed peak performance because you haven't given them the tools to do that.

Paul McCartySo you're gonna get B team and c team players right because that's what you're giving them.

Jenn GileI think on the other side though there's also an argument to be made that developers haven't you know really brought themselves towards the security thing because there was always well the security team was doing that and they're idiots they can't do it right they don't know they don't know how the software sausage is made oh I totally yeah Jen's wrapping me up but it but the reality is the reality is that developers need to come the both teams need to come towards the middle and that was what DevSecOps was supposed to deliver for us but it just hasn't happened right that's well ending on a positive note I think this has been a really interesting conversation you know to listen to what you went through and how hard it was and how hard it continues to be I think I'm trying to picture you trying to do this maybe two or three years ago without agents and how prohibitively expensive and difficult it would have been.

Jenn GileSo I think we're hearing generally a success story, but man it's still hard.

SPEAKER_00Yeah yeah I I did an estimate it was it would to clean everything up and lock everything down it would have taken me personally probably full time three months.

Jenn GileWow yeah and then what happens to your open source projects at that point.

Paul McCartyYep exactly exactly one your family and your like how you make money and all the other things that we have to do too as well that you're juggling as well yeah well let us let us know if open source malware can help out in in any way and you know just you know feel free to reach out anytime to me personally or to Jen. Um you know if you want to be part of the solution.

SPEAKER_00Awesome cool thank you yeah thanks cool thanks buddy cheers mate

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. React2STEAL hits Node.js/React shops, MSFT official agent-framework compromised

    Nov 18, 202642 minAudio

    This week we talked about: React2STEAL: An automated hacking framework runs entirely on GitHub Actions inside 45 compromised GitHub repositories. It scans for React2Shell and commits stolen credentials back to those...

    Credit the people on this episode

  2. Trojanized Claude Code extension, Binance and Polymarket thefts, PolinRider dated to 2025

    Nov 6, 202647 minAudio

    This week we talked about: Trojanized Claude Code extension: On October 29, a trojanized Claude Code extension was shipped from Cursor's own mirror of the Open VSX registry. Cursor's mirror can carry different versions...

    Credit the people on this episode

  3. Brotli vulnerability, LiteLLM breached via unrevoked key, poisoned prompt downloads malware

    Oct 28, 202631 minAudio

    This week we talked about: Brotli vulnerability: The Brotli decoder bug behind Node2Shell reaches far beyond Node, and it's been overshadowed by the hype around PHP2Shell. Google's Brotli C code is usually vendored into...

    Credit the people on this episode

  4. OVH CLI compromised by Glassworm, compound payloads hide malware, GhostAction copycats PolinRider

    Oct 21, 202642 minAudio

    This week we talked about: OVH CLI compromised by GlassWorm: GlassWorm is back. The Russian threat actor went quiet after its infrastructure was taken down earlier this year, and it resurfaced with malicious versions of...

    Credit the people on this episode

  5. GitHub security improvements, GhostAction phishes OSS maintainers, and DoJ shuts down DPRK laptop farms

    Oct 15, 202627 minAudio

    This week we talked about: GitHub push attribution: GitHub now shows when the account that pushed a commit is different from the one listed as the committer, which makes faked Git history easier to spot. That could help...

    Credit the people on this episode