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

DevSec Station

DevSec Station artwork

NPM Supply Chain Attack: Active Worm Stealing Tokens, SSH Keys, and Credentials

Apr 22, 20262 minAudio

🚨 Emergency DevSec Station update. There’s an active npm supply chain attack happening right now. Malicious npm packages are running install scripts that quietly steal: • SSH keys • AWS credentials • GitHub tokens • Browser passwords • Crypto wallets From there, the attack uses your npm publish token to spread into every package you maintain. That’s how this turns into a worm across the npm ecosystem. This is not theoretical. It’s already in the wild. 👉 Immediate fix: Run npm config set ignore-scripts true This disables install scripts and blocks the main attack path. If you work in JavaScript, Node.js, DevSecOps, or application security, take action now and tell your team. Watch the full 2 minute breakdown and share this with anyone who installs npm packages. #npmSecurity #SupplyChainAttack #DevSecOps #AppSec #JavaScriptSecurity #CyberSecurityAlert DevSec Station is a podcast by Tanya Janca (SheHacksPurple), focused on short, practical lessons that help software developers build more secure software. Train with Tanya: Want to bring practical, hands-on secure coding, application security, or AI security training to your team? Learn more at SheHacksPurple. Follow Tanya: https://newsletter.shehackspurple.ca https://linkedin.com/in/tanya-janca https://youtube.com/@shehackspurple https://shehackspurple.ca

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.

SPEAKER_00Hi, I'm Tanya Janka, also known as SheX Purple, and I'm interrupting our regular DevSec station programming because I don't feel that this can wait. There's an active NPM supply chain attack happening right now. I know there's been a lot of them recently, but this one is a big one, and I wanted to tell you about it. Packages that look completely normal and legitimate are being compromised and published with malicious versions that are stealing your credentials. It's the moment that you run NPM install when it steals it via post-install script.

SPEAKER_00They're taking SSH keys, AWS credentials, GitHub tokens, browser passwords, crypto wallets, literally everything that it can grab, it is stealing from you. And then it will use your published token to infect every single package that you maintain. I would call this attack a worm. So here's what I would like you to do right now. If you could open your terminal and run the following command, which obviously you will decide for yourself, but this is a request, not a demand.

SPEAKER_00npm config set, ignore dash scripts. True. What this will mean is that post-install scripts don't run anymore. So I just want you to run one command which tells npm to never automatically run a post-install script again without your explicit permission. I realize that occasionally a legitimate package will break as a result of this. I that's it might sound weird, but I want this. Um, this will be friction, and I want us to treat it as a feature, a security feature, not a bug.

SPEAKER_00It's alerting you that something's happening. It means that you have to consciously decide to trust the script before it runs on your machine. Um, that's how this would work from now on. So instead of post-install scripts that are potentially malicious running automatically, the post-install script would come to your attention. You review it and decide that it is good. Um, I would hope that you could set this for every org, for every project, for every developer on your team. That is what I would like. I want you to set it for yourself today. Um I'd like you to talk to your team about setting it for everyone as soon as possible.

SPEAKER_00Um, on top of this, if you could run a software composition analysis tool, also known as SCA, um, they can catch these sort of things fairly often, fairly quickly. If you could do both, you'd get even better results. Uh, thank you very much. Um, I will be back with your regularly scheduled programming next episode. Thank you.

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. Let's Threat Model an AI Agent Escape

    Nov 19, 202620 minAudio

    What happens when an AI agent crosses a security boundary it was supposed to respect? How do we prevent an agent from accessing unauthorized systems, exposing secrets, or finding an unexpected path into production? In...

    Credit the people on this episode

  2. What Permissions Should You Give an AI Agent?

    Nov 5, 202613 minAudio

    Your AI agent can read files, execute commands, install software, connect to external services, and maybe even deploy to production. But should it have permission to do all of those things? In Season 2, Episode 3 of...

    Credit the people on this episode

  3. Special Bulletin: PHP2Shell, Critical PHP Vulnerabilities Developers Need to Know About

    Oct 22, 20266 minAudio

    Two critical PHP vulnerabilities have been disclosed, and even applications written with secure coding practices may be affected. In this special bulletin of DevSec Station, Tanya Janca (SheHacksPurple) explains...

    Credit the people on this episode

  4. What Can Your AI Agent Actually Do?

    Oct 22, 202612 minAudio

    I asked Claude to build me a little application that would greet me every morning. Nothing complicated. Just say hello, call me a Queen, give me a compliment, and share an inspirational quote. Cute, right? Except Claude...

    Credit the people on this episode

  5. Your AI Worked 59 Times. What About the 60th?

    Oct 8, 20269 minAudio

    What happens when your AI assistant does exactly what you expect 59 times... and then does something completely bananas on the 60th? While teaching a secure coding class, I watched nearly 60 students use the same AI...

    Credit the people on this episode