Threat actors published 600+ malicious versions to npm as part of the Shai-Hulud supply chain campaign; most of the affected packages are in the @antv ecosystem
Threat actors earlier today published more than 600 malicious packages to the Node Package Manager (npm) index as part of a new Shai-Hulud supply-chain campaign.
Context & Ripple Effects
Related coverage shows a recurring series of package-registry compromises: an earlier Axios incident was followed by compromises affecting packages tied to SAP, Intercom, Mistral, UiPath, and TanStack tools. The latest campaign expands that pattern into a large cluster concentrated in the @antv ecosystem.
The repeated Shai-Hulud/Mini Shai-Hulud attribution in the coverage matters because it suggests maintainers and downstream users must treat registry trust as an active operational risk rather than an isolated package incident.
First-order effects
- Teams using affected @antv npm packages face an immediate need to identify malicious versions, halt upgrades or deployments involving them, and replace or roll back compromised dependencies.
- @antv package maintainers and npm ecosystem responders must triage a high-volume publication event, including package ownership, release history, and downstream exposure.
Second-order effects
- Application vendors that inherit @antv packages through transitive dependencies will need to extend software-composition reviews beyond their direct dependency lists, increasing remediation work across customer-facing builds.
- The concentration of incidents in widely reused developer packages raises the cost of maintainer-account security failures, pushing package publishers and enterprise consumers toward tighter release controls and dependency provenance checks.
Third-order effects
- If successive incidents continue to move across prominent npm ecosystems, package registries and major consumers may increasingly treat publisher identity and release integrity as prerequisites for adoption, not optional security signals.
- The pattern could accelerate a bifurcation between dependencies backed by stronger verification and monitoring practices and the broader long tail of packages whose update risk is harder for downstream users to assess.
The trend: This is another data point in the shift from isolated open-source package compromises to repeated, ecosystem-scale attacks that exploit the trust relationships embedded in software dependency distribution.