How NPM Auto-Updates & Post-Install Scripts Could Hijack Your Org

In this Modern Web Podcast, Rob Ocel and Danny Thompson break down the recent string of NPM supply chain attacks that have shaken the JavaScript ecosystem. They cover the NX compromise, the phishing campaign that hit libraries like Chalk, and the Shy Halood exploit, showing how small changes in dependencies can have massive effects. Along the way, they share practical defenses like using package lock and npm ci, avoiding phishing links, reviewing third party code, applying least privilege, staging deployments, and maintaining incident response plans. They also highlight vendor interventions such as Vercel blocking malicious deployments and stress why companies must support open source maintainers if the ecosystem is to remain secure. Key Points from this Episode: - Lock down installs. Pin versions, commit package-lock.json, use npm ci in CI, and disable scripts in CI (npm config set ignore-scripts true) to neutralize post-install attacks. - Harden people & permissions. Phishing hygiene (never click-through emails), 2FA/hardware keys, least-privilege by default, and separate/purpose-scoped publishing accounts. - Stage & detect early. Canary/staged deploys, feature flags, and tight observability to catch dependency drift, suspicious network egress, or monkey-patched APIs fast. - Practice incident response. Two-hour containment target: revoke/rotate tokens, reimage affected machines, roll back artifacts, notify vendors, and run a post-mortem playbook. Rob Ocel on Linkedin: https://www.linkedin.com/in/robocel/ Danny Thompson on Linkedin: https://www.linkedin.com/in/dthompsondev/ This Dot Labs Twitter: https://x.com/ThisDotLabs This Dot Media Twitter: https://x.com/ThisDotMedia This Dot Labs Instagram: https://www.instagram.com/thisdotlabs/ This Dot Labs Facebook: https://www.facebook.com/thisdot/ This Dot Labs Bluesky: https://bsky.app/profile/thisdotlabs.bsky.social Sponsored by This Dot Labs: https://ai.thisdot.co/