Shai Hulud npm package attack
Something called Shai Hulud — named, apparently, for the sandworms of Dune, creatures that swallow everything whole — surfaced on May 12th when researchers flagged a supply chain attack targeting npm, the package registry that sits beneath the daily work of millions of JavaScript developers. The initial strike was surgical: malicious versions of packages mimicking TanStack and Mistral AI libraries, both signed to look legitimate, were pushed into the registry. Signed packages carry an implicit trust signal. That was the point. Then, a week later on May 19th, the picture got considerably worse. A second wave. Not two packages this time — 600. The operation had scaled, or the first disclosure had triggered a scramble to find how far the infestation already ran, depending on how you read the timing. Either way, 600 compromised packages in a single ecosystem is not a footnote.
If confirmed, here is what this means. The signing mechanism that developers rely on to verify package authenticity has been weaponised, which is the kind of trust-poisoning that takes years to fully repair. Any project that pulled a TanStack or Mistral dependency between May 12th and discovery — or any of the 600 packages identified in the second wave — should treat their environments as potentially compromised. The second-order effect matters more: developers may now face audit fatigue across hundreds of transitive dependencies they never consciously chose to install. For enterprises shipping JavaScript at scale, this is a supply chain audit event. For the broader npm ecosystem, it is another data point in the uncomfortable argument that the registry's governance and verification infrastructure is not keeping pace with the threat environment.
Watch for npm's official incident report and whether the package registry implements emergency revocation or enhanced signing verification in response — either would confirm the severity of the second wave and clarify how long the malicious packages were live before detection.
TeamPCP, the threat actor behind the recent supply chain attack spree, has been linked to the compromise of the npm and PyPI packages from TanStack, UiPath, Mistral AI,
Cybersecurity researchers have discovered a fresh software supply chain attack campaign that has compromised various npm packages associated with the @antv ecosystem as part of
The attacks are part of a wider campaign known as Mini Shai-Hulud, which has already compromised several open source projects and, in turn, developers and companies that use them.
Cybersecurity researchers have flagged yet another evolution of the supply chain attack linked to the Mini Shai-Hulud, Miasma, and Hades malware family that has compromised a new
Self-propagating malware named 'ChainDrop' has compromised more than 1,300 packages with a combined 2 billion monthly downloads on the Node Package Manager (npm) registry. [...]
Mandiant says an attacker hijacked an active AI coding-assistant session at an unnamed software-as-a-service provider and later spread Shai-Hulud across about 100
A new supply chain attack targeting the Node Package Manager (npm) ecosystem is stealing developer credentials and attempting to spread through packages published from compromised
Hackers have injected credential-stealing malware into newly published versions of node-ipc, a popular inter-process communication package, in a new supply chain attack targeting
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →