AN
Ahmad Nassri

Ahmad Nassri

Things Ahmad Says on Podcasts

Where to Find Them

Ahmad Nassri has been a guest on JS Party: JavaScript, CSS, Web Development (3 times) and The Changelog (2 times) .

Recently: “All your packages are belong to us (Interview)” on The Changelog (November 2026); “Best of the fest! Volume 1” on JS Party: JavaScript, CSS, Web Development (November 2021); “Let's replace your kidney with React” on JS Party: JavaScript, CSS, Web Development (September 2020); “Modular software architecture” on JS Party: JavaScript, CSS, Web Development (December 2019); “Kong, APIs, Microservices (Interview)” on The Changelog (December 2015).

What They Said

“Nowadays, we're like less than a day. It's almost happening in the same day where an actual security vulnerability is being disclosed and being exploited, meaning companies are actually being penetrated or data is being sold or something is happening on the same day.” — Ahmad Nassri, The Changelog

Ahmad points to a site that plots the time between a vulnerability's disclosure and its exploitation. He says the gap used to be a year or two.

The Changelog · 2026-11-13 Permalink → Listen →
The Changelog Around 1:36:51 into the episode
Ahmad Nassri

…just supply chain attacks. It's also vulnerabilities that are being disclosed at a much rapid rate than ever before. I think there's a website for the audience, if they're not familiar with Time2Exploit, I think it's called. Oh, is that right? Let me see what the website is. Oh, zerodayclock.com.

Adam Stacoviak

Oh.

Ahmad Nassri

It has a plot of the from vulnerability to exploitation over the last, let's say, 10 or so years. And you can see that number coming slower and slower, where like, you know, a security researcher in the past would find some bad, you know, security vulnerability in some open source software. They would disclose it. And then before anybody's actually seen it being exploited in the world, in the real world, it might take, you know, back then it would take a year or two, but then that number keeps dropping. Nowadays, we're like less than a day. It's almost happening in the same day where an actual security vulnerability is being disclosed and being exploited, meaning companies are actually being penetrated or data is being sold or something is happening on the same day. TTELT hours now.

Adam Stacoviak

Gosh, man. Yeah. Yeah. This is that's interesting. The meantime for TTE totally is dropping. 2018 was 2.3 years and here we are in 2026. It's eight hours.

Ahmad Nassri

I think it's going to get worse.

Adam Stacoviak

Yeah, obviously. I mean, it'll get to basically, it won't be a zero day anymore. It'll be zero microseconds like that. Oh my gosh. So what does a developer to do? Do you just scrutinize your dependencies even more than we've already done? Build versus buy is always the case, right? And then, even…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“Which is the insecure thing? Is it the package or is it the agent all of a sudden on your machine? … Now we're not looking at data exfiltration baked into the code. We're looking at prompts that on the surface seems like this package is meant to prompt an AI agent. But the prompt itself is the malicious thing, not the code, the code in the package.” — Ahmad Nassri, The Changelog

Ahmad describes a package worm variant whose code looked clean but told whatever AI agent was installed to scan the machine and upload secrets. Code-level analysis misses it because the payload is a prompt.

The Changelog · 2026-11-13 Permalink → Listen →
The Changelog Around 45:53 into the episode
Ahmad Nassri

…of time, even though the package version doesn't change. So this multifaceted approach is challenging for anybody in a centralized position to keep up on top of and keep tracking. That's why companies like Socket exist to help keep you safe and keep your AI agents from making the wrong choices.

Adam Stacoviak

…and that's just the nature of the beast. From the packum to how the tarball is immutable, what the package gets added to. There's a lot of detail in the NPM registry design down to the artifact level that seems really, really strong. Which one has the best security envelope to you, in your opinion?

Ahmad Nassri

…prompt that AI agent to go and do telemetry scanning and do kind of pen testing on your machine, find any environment variables, find any of that stuff, and then upload it to a GitHub repo. So like which is the insecure thing? Is it the package or is it the agent all of a sudden on your machine? So like even from an analysis perspective, if you look at the code, that code might look safe. But now we're not looking at data exfiltration baked into the code. We're looking at prompts that on the surface seems like this package is meant to prompt an AI agent. But the prompt itself is the malicious thing, not the code, the code in the package.

Adam Stacoviak

Yeah. There's a lot of directions you can go with that. I mean, I think the one thing I think about with NPM in particular, let's just focus on that, is things like: can DNS solve the issue? So if it's at the CI level, it could be simply, well, if you're going to call out to any other place, we're…

Ahmad Nassri

Again, I think victim of the popularity of JavaScript and Node.js in general. And maybe this is something like NPM's fault at the early days, if you want to call it that, or lack of foresight, if you will. But if you look, for example, at NPM the registry or NPM the CLI as well, the initial kind of…

Adam Stacoviak

Yeah, there's a lot that there's a lot there. I think, you know, how is NPM being governed and ran is, you know, I don't know much. It's very opaque in terms of who's on the inside. And I think GitHub's been a bit more vocal about it, but not still not enough, in my opinion, to understand. And…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“A year ago… across all versions of all packages… maybe there's like 4,000 a week. A package gets compromised and then like 20 versions, 30 versions of it get pushed. You can add that up to about 4,000 different artifacts that are compromised packages across all ecosystems, not just NPM. Nowadays, we're seeing close to 12,000 and that number keeps growing per week.” — Ahmad Nassri, The Changelog

Adam asked for a tour of a year of supply chain attacks. Ahmad, CTO of Socket and former CTO of npm, gives Socket's own count of compromised package artifacts per week, then and now.

The Changelog · 2026-11-13 Permalink → Listen →
The Changelog Around 1:08:19 into the episode
Ahmad Nassri

Yeah, I think there's been a meme going around on at least on Twitter that I've seen that, I don't know if you've seen it, like the cat meme, which says on the top, I wake up and there's a whole circle at the bottom says new supply chain attack. And then the circle goes back.

Adam Stacoviak

Pretty much.

Ahmad Nassri

…coincident. It's not like we're being very efficient at finding these things to the point where it's almost a daily occurrence. I think the, if you had asked me maybe like, let's go back maybe a year, you know, how often do these things happen? How often is there a supply chain attack? From our numbers, what we've kind of tracked and seen, you know, at the time, I would have said, you know, across all versions of all packages, if you want to like take a holistic number, like maybe there's like maybe 4,000 a week. You know, a package gets compromised and then like 20 versions, 30 versions of it get pushed. Like you can add that up to about 4,000 different artifacts that are compromised packages across all ecosystems, not just NPM. Nowadays, we're seeing close to 12,000 and that number keeps growing per week. We're…

Adam Stacoviak

new. This is brand new. This

Ahmad Nassri

is all new. And then we start seeing the same things happen with, like I said, IDE extensions, where maybe the IDE extension itself is not compromised, but it's going to try to download a package or download some dependency after it's run and then try to impact the local environment as well. And…

Adam Stacoviak

I've seen this too with MCP servers as well, where like you'll auth to an MCP server and you expect it to not change and then it changes. And so you're still calling the same MCP workflow and the response changes. There's poisoning happening in lots of different layers across the spectrum. It's…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In