flawopen.com/घटनाएं (Incidents)/Shai-Hulud npm worm

Shai-Hulud: npm इकोसिस्टम का वह साइबर वर्म जो बिना इंसानी मदद के खुद को पब्लिश करता गया

Critical — Ecosystem-wide CWE-506: Embedded Malicious Code September 2025
सरल भाषा में समझें (ELI5)

कल्पना कीजिए कि कई कारखानों का नेटवर्क है जहाँ एक का सामान दूसरा बिना जांचे तुरंत इस्तेमाल करता है। किसी ने एक कारखाने के मैनेजर का आईडी कार्ड चुरा लिया और एक डिब्बा भेजा। जैसे ही अगले कारखाने में डिब्बा खुला, उसमें से एक स्वचालित मशीन निकली जिसने उस कारखाने के कार्ड भी चुराए और नए डिब्बे बनाकर आगे भेज दिए। इसे किसी इंसान को चलाने की ज़रूरत नहीं रही — यह खुद फैलता गया।

Defences that would have mattered

The transferable lesson

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.

FAQ

How do I tell whether I was affected?

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.

Does --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.

Was this a one-off?

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.

स्रोत और आधिकारिक एडवाइजरी