CyberSecurity SEE

Mini Shai-Hulud Affects Hundreds of npm Packages in the AntV Ecosystem

Mini Shai-Hulud Affects Hundreds of npm Packages in the AntV Ecosystem

Large-Scale Supply Chain Attack: The Resurgence of Mini Shai-Hulud Worm

The digital landscape is facing a renewed threat as the Mini Shai-Hulud worm makes a significant comeback, affecting hundreds of packages within the npm ecosystem, particularly those linked to the AntV data visualization framework. This latest wave signals one of the largest coordinated attacks observed to date, with an onslaught of malicious activity that unfolded in a remarkably brief timeframe—approximately one hour.

An analysis conducted by Socket’s Threat Research Team reveals that the attack commenced around 01:56 UTC on May 19. During this time frame, cybercriminals managed to disseminate 639 malicious versions across 323 unique npm packages. The rapid nature of this campaign has raised alarms within the tech community regarding the vulnerability of software supply chains.

To provide further insight into the matter, Microsoft has stepped in with updates stemming from its ongoing investigation into the supply chain attack. The tech giant, which has previously issued guidance through its Defender platform regarding the broader Mini Shai-Hulud threat, has shared essential findings via the social media platform, X, on the same day the assault took place.

Among the impacted packages are some high-traffic npm dependencies that developers heavily rely on. Notable mentions include echarts-for-react, size-sensor, @antv/scale, and timeago.js. The compromised npm maintainer account, known as "atool," had publishing rights over more than 500 packages, marking a serious breach of trust and security.

A Familiar Tactic with a Twist

Each malicious version released during this attack incorporated a preinstall hook within the package.json file, executing a sophisticated 498 KB obfuscated Bun bundle. This bundle’s primary function was to harvest sensitive information, including cloud credentials, CI/CD tokens, SSH keys, Kubernetes service account tokens, and local password manager vaults.

The stolen data was then exfiltrated through public GitHub repositories set up using the compromised tokens. These repositories cleverly employed terminology from Frank Herbert’s Dune universe, alongside descriptions containing a reversed marker that read, “Shai-Hulud: Here We Go Again.” This deliberate choice of nomenclature underscores the attackers’ strategic intent and their understanding of systemic vulnerabilities.

Avital Harel, security research lead at Upwind, commented on the sophistication of the attack, suggesting that the operators demonstrated a mature understanding of security measures. Harel noted that the design of this campaign was not only aimed at propagation but intentionally crafted to complicate the analysis and detection of malicious activity.

"This campaign was not only built to spread, but also to slow down analysis," Harel stated, emphasizing the premeditated nature of this operation.

Patterns and Consequences

According to Socket, the attack represents a broader pattern of high-volume compromises within the npm ecosystem, characterized by coordinated malicious publications. To date, the firm has documented 1,055 compromised versions stemming from a total of 502 unique packages across npm, PyPI, and Composer ecosystems.

Meanwhile, StepSecurity reported having documented more than 2,500 GitHub repositories featuring markers linked to this campaign. The ongoing activity has been attributed to a financially motivated threat group known as TeamPCP.

The recent attack also extends the payload-delivery techniques used in previous waves, representing a worrying continuation of established malicious strategies. A significant portion of the harmful versions has injected an optionalDependencies entry that points toward orphan commits in an unrelated trustworthy repository—specifically, the antvis/G2 project.

This manipulation involves creating forged authorship that matches a legitimate maintainer of the project, effectively disincentivizing closer scrutiny of the compromised commits. GitHub employs a system that stores commits within a shared object pool across a repository’s fork network, allowing attackers to exploit the npm’s github: resolver. This resolver can fetch by commit hash without verifying the origin of a commit, thereby facilitating the delivery of malicious code.

Isaac Evans, founder and CEO of Semgrep, elaborated on the structural issues plaguing the trust model of dependencies. He warned, "A package you have trusted for years can suddenly become the delivery mechanism," indicating a critical vulnerability within supply chain strategies.

In response to these threats, Snyk has urged organizations to treat any secrets accessed during installation as compromised. Organizations are advised to implement several protective measures, including pinning dependencies to versions published before May 19, rotating credentials exposed to affected build environments, and conducting thorough audits of GitHub accounts for unauthorized repository creation matching the Dune-themed naming conventions observed in this campaign.

The surge of the Mini Shai-Hulud worm poses not just an immediate threat, but also a long-term challenge for software security, necessitating a reevaluation of trust within the software ecosystem and a commitment to robust protective measures across the industry.

Source link

Exit mobile version