npq

to-publish malicious versions → Why “upgrade everything in CI” is one of the most dangerous patterns a dev team can adopt → What actually happened in recent maintainer compromises and dependency hijacks → How MCP servers introduce entirely new attack vectors: toxic flows, prompt injection, shadowed tools, and tainted context → Why AI-generated code is statistically insecure and how to loop security scanning into the agent workflow → The SQL injection, command injection, and path traversal bugs Liran keeps finding in real MCP servers → The XZ Utils incident and how a 500ms delay uncovered a nation-state backdoor → When UX decisions accidentally create security holes (XSS, anonymous actions, permission gaps) If you install dependencies, use AI coding agents, or maintain any production-facing Node.js or frontend systems, this conversation will probably make you rethink your threat model. Watch: https://youtu.be/tks03l1E0IQ Listen: https://open.spotify.com/episode/1zs8TL4sSfKUBLkTgPXeML Apple: https://podcasts.apple.com/us/podcast/security-at-scale-with... More from Liran: GitHub: https://github.com/lirantal NPQ Package Checker: https://github.com/lirantal/npq Snyk Blog: https://snyk.io/blog LinkedIn: https://linkedin.com/in/talliran If you're dealing with supply chain risk, AI code generation, or insecure dependencies, you’ll get a lot from this one.

alicious version. * There's quite a few tools to help mitigate the risk here, like https://socket.dev and npq (https://github.com/lirantal/npq). As one datapoint, look at the download stats for the affected Chalk package for example (https://www.npmjs.com/package/chalk?activeTab=versions) - the vast majority of installs were not installing the latest version anyway. There are caveats to this: e.g. you can use npm without a lockfile, in which case a fresh local install can pull down unexpected versions, or you could be manually updating/adding a different package which happens to depend on an affected package (which might trigger a lockfile update, which might then fetch the latest version of the subdependency) during the vulnerable window, or of course it's totally possible you might install the package for the first time at the precisely wrong moment, etc etc. This is definitely bad, and could have been extremely disastrous if it wasn't caught. But in practice, npm & the ecosystem have put in quite a few protections that do help to _mostly_ mitigate these kind of risks in typical use cases (but not completely, and there's definitely plenty more work to do!) and it's certainly not the case that millions of JS developers & projects were all catastrophically pwned today.