Malicious npm Campaign Hits Popular AntV and ECharts Packages
On 19 May 2026, researchers disclosed a 'Mini Shai-Hulud' malware campaign that compromised the 'atool' maintainer account on npm, injecting credential-stealing code into AntV-related packages, including 'echarts-for-react' with about 1.1 million weekly downloads. The attack targeted developer environments and CI/CD credentials.
Key Takeaways
- A targeted npm malware campaign dubbed "Mini Shai-Hulud" compromised the "atool" maintainer account, affecting multiple AntV-related packages.
- The popular library echarts-for-react, with roughly 1.1 million weekly downloads, was among the impacted packages.
- Malicious code was designed to steal credentials from developer environments and CI/CD systems, posing widespread supply-chain risks.
Around 04:56–04:57 UTC on 19 May 2026, security researchers revealed that a coordinated malware operation—codenamed "Mini Shai-Hulud"—had infiltrated the npm ecosystem by compromising the "atool" maintainer account. The attackers used this access to push malicious updates to several AntV-related packages, including echarts-for-react, one of the most widely used charting libraries for React applications with an estimated 1.1 million weekly downloads.
The injected code was tailored to exfiltrate credentials and sensitive data from developer machines and CI/CD environments, indicating a focus on penetrating enterprise infrastructure through trusted open-source dependencies.
Background & Context
Npm, the primary package registry for the JavaScript ecosystem, has been a frequent target for supply-chain attacks due to its centrality in modern web and server-side development. By compromising a single widely used package or maintainer, adversaries can quietly reach thousands of downstream applications and organizations.
The "Mini Shai-Hulud" campaign follows a pattern seen in previous npm attacks, where adversaries either gain control of maintainer accounts via credential theft, phishing, or social engineering, or exploit abandoned packages by offering to "help" maintain them. Once access is secured, malicious code can be inserted as a minor version update, often going unnoticed until anomalies are detected.
In this case, targeting AntV-related tools and echarts-for-react is especially impactful, as these libraries are widely used in data visualization dashboards, internal admin tools, and analytics platforms across industries.
Key Players Involved
The key actors include:
-
Threat Actors: The group behind Mini Shai-Hulud, whose precise identity and origin are not yet publicly attributed. Their tactic of embedding credential-stealing payloads suggests a goal of gaining broader access to corporate infrastructure, not just end-user devices.
-
"atool" Maintainer: The maintainer account was leveraged as the entry point. Whether the account owner was directly compromised or the credentials were reused elsewhere remains under investigation.
-
Npm and Parent Platform Operators: Responsible for detecting and removing malicious packages, notifying affected users, and tightening account security controls.
-
Affected Organizations: Any developers or companies that recently installed or updated the compromised packages. Their exposure depends on whether builds pulled the infected versions and what environment variables, config files, or tokens were accessible.
Why It Matters
The campaign is significant for several reasons:
-
High-Volume Distribution: With echarts-for-react alone reportedly delivering around 1.1 million downloads per week, even a short-lived malicious release could impact a broad segment of the JavaScript ecosystem. Many organizations may not have immediate visibility into which microservices or applications rely on the compromised packages.
-
Credential Theft Focus: By aiming at CI/CD credentials and developer environment secrets, attackers can move laterally into critical systems, including production environments, cloud infrastructure, and internal tooling. Such access can be used for data theft, ransomware deployment, or insertion of additional backdoors.
-
Trust in Open Source Ecosystems: The incident further stresses the open-source trust model. Enterprises that depend on npm and similar registries must contend with the reality that widely used packages may be compromised at any time, requiring greater emphasis on dependency governance and code auditing.
Regional and Global Implications
This incident has global reach. The affected packages are used worldwide by organizations in finance, e-commerce, SaaS, media, and government. The scale of potential exposure means that follow-on intrusions may be uncovered over weeks or months as compromised credentials are leveraged.
Regulators and industry bodies focused on critical infrastructure and software security will likely cite this case as evidence supporting stricter software supply-chain requirements. This could accelerate adoption of standards around provenance, code signing, and secure development lifecycle (SDLC) practices.
For cloud providers and large technology firms, the attack is a reminder that their customers’ security posture is tied closely to the integrity of shared open-source components, a factor increasingly considered in risk assessments and shared-responsibility models.
Outlook & Way Forward
In the immediate term, organizations must take urgent steps to assess and mitigate exposure:
- Identify all applications and services that depend on the compromised AntV and echarts-for-react packages.
- Pin versions to known-good releases and remove any infected versions from internal package caches.
- Rotate credentials and tokens that may have been accessible to build and runtime environments using the affected libraries.
Npm operators and the broader security community are likely to publish detailed indicators of compromise (IOCs), timelines of malicious versions, and remediation guidance. Security teams should integrate this intelligence into their detection and response workflows.
Over the longer term, this and similar incidents will accelerate the shift toward more rigorous dependency management practices. Likely changes include broader deployment of automated tools to audit dependencies for known malicious versions, stronger MFA and behavioral analytics for maintainer accounts, and increased use of lockfiles and internal registries to control what enters production builds.
The Mini Shai-Hulud campaign also underscores the need for cultural and organizational changes: treating open-source components as critical third-party vendors that require ongoing risk evaluation. As more organizations internalize this mindset, demand for verifiable supply-chain security—such as signed artifacts, reproducible builds, and SBOMs—will grow, reshaping how open-source ecosystems operate and are governed.
Sources
- OSINT