flawopen.com/Incidents/Shai-Hulud npm worm
Imaginez une chaîne d'usines où chaque colis reçu est déballé et intégré sans vérification. Un malfaiteur dérobe un badge et expédie un colis piégé : dès l'ouverture dans l'usine suivante, le piège subtilise les badges locaux et expédie aussitôt de nouveaux colis piégés. Le ver se reproduit exponentiellement sans pilote.
npm ci --ignore-scripts neutralises the execution primitive this worm depended on. Allowlist the small number of dependencies that truly need a native build step.npm ci, not npm install. A lockfile means a freshly published malicious version is not silently pulled into your build the hour it appears.Most dependency-security tooling is built to answer "does this package have a known CVE?". A freshly trojanised version of a package you already trust has no CVE, a legitimate history, and a maintainer in good standing. Shai-Hulud is the argument for treating installation itself as the security boundary — controlling what executes, what credentials are within reach when it does, and how quickly new versions are adopted — rather than relying on after-the-fact vulnerability lists.
Check whether any affected package version appears in your lockfiles or CI logs for the exposure window, look for unexpected public repositories or new Actions workflows on developer and organisation GitHub accounts, and audit npm and GitHub token creation and package publication events. If a build machine ran an affected version, treat every credential that machine could reach as compromised and rotate it.
--ignore-scripts fully protect me?It removes the install-time execution path, which is what this worm used. It does not protect you from malicious code inside a package you actually import and run. It is a strong control, not a complete one.
No. Further variants using the same self-propagating pattern were reported in late 2025 and into 2026, and the technique has since been observed spanning multiple registries. The structural weaknesses it exploits — automatic script execution and long-lived publish tokens — are properties of the ecosystem rather than of any one package.