Modified Shai-Hulud Worm Variant Spotted on npm Registry — New Malware Strain Under Testing

Cybersecurity researchers have identified a modified strain of the notorious Shai-Hulud malware on the npm JavaScript package registry, marking the latest evolution in a series of high-impact software supply chain attacks that have rocked the open-source ecosystem since mid-2025. The discovery suggests that threat actors behind this worm-style malware continue to evolve their tactics and may be preparing for future attacks, even though the current payload appears limited in spread.

Unlike previous waves of the Shai-Hulud campaign — which rapidly spread by stealing credentials and pushing malicious updates into widely used npm packages — this new variant appears to be in an early testing or “proof-of-concept” phase. It contains notable changes to obfuscation, payload structure, and error handling, raising serious concerns for developers, open-source maintainers, and enterprises that depend on npm packages in their software supply chains.

Below is a comprehensive look at the modified Shai-Hulud worm, its technical innovations, the risks it poses, and how developers and organizations can protect themselves.

What Is the Shai-Hulud Worm? A Brief Recap

The Shai-Hulud malware campaign first emerged in September 2025 as a supply chain attack targeting npm, the default package registry for the JavaScript ecosystem. Instead of conventional malware tactics that exploit vulnerabilities, this campaign took advantage of the inherent trust model of open-source packages: if a package is trusted and widely used, code embedded in it is assumed to be safe.

Shai-Hulud’s core capabilities included:

Compromising developer npm accounts
Injecting malicious code into legitimate packages
Harvesting sensitive credentials such as API keys, cloud tokens, CI/CD secrets, npm, and GitHub tokens
Automated propagation into other packages using stolen tokens, creating a worm-like expansion through the ecosystem

The malware’s self-replicating design and exploitation of trust in package registries made it one of 2025’s most significant supply chain threats — affecting libraries and applications of all sizes.

New Shai-Hulud Variant Found on npm

On December 28, 2025, researchers at security firm Aikido discovered an updated version of the Shai-Hulud worm embedded in the npm package @vietmoney/react-big-calendar — a library originally published in March 2021 by a user identified as “hoquocdat.”

This package had not been updated since its initial release until the recent version 0.26.2 appeared with the novel malware payload. Since that update, it was downloaded nearly 700 times, indicating moderate exposure to developers before researchers intervened.

Security teams analyzing the code noted:

Obfuscation changes that make detection harder.
Renamed payload files, such as bun_installer.js and environment_source.js.
Removal of the “dead man switch”, a previously observed mechanism that triggered destructive behavior if no credentials were harvested.
Adjusted order of operations for scanning data and collecting secrets.

These modifications suggest the malware is being fine-tuned or tested rather than immediately unleashed at scale — a worrying sign that future variants may be more effective and stealthy.

Testing, Not Full Deployment — Yet

Unlike previous Shai-Hulud waves — which rapidly spread across thousands of repositories and stole vast amounts of secrets — researchers have not observed significant infections resulting from the latest packaged strain. According to security expert Charlie Eriksen, the limited spread implies this variant could be a testing payload rather than a fully operational attack.

Eriksen noted that the code appears to have been obfuscated anew rather than altered in place, and its differences from earlier strains indicate development by someone with access to the original malware source. This raises the possibility that the group behind the first Shai-Hulud campaigns — or collaborators with insider knowledge — is preparing next-generation tooling.

While the lack of widespread infection is a positive sign for now, the discovery should not be interpreted as reassurance. Instead, it may signal that further refinements are underway, potentially enabling a more destructive future campaign.

How the Malware Could Function (Based on Past Waves)

Although the current version appears limited, Shai-Hulud’s previous behavior offers clues about its potential impact if activated at scale:

Credential Harvesting

Earlier versions of the malware scanned developer systems for credentials such as:

Cloud service tokens (AWS, GCP, etc.)
npm and GitHub access tokens
CI/CD pipeline secrets

These were then exfiltrated to attacker-controlled repositories using stolen credentials.

Self-Propagation

Once harvested, tokens could be abused to:

Access the developer’s npm account.
Modify additional packages maintained under the account.
Publish malicious versions of those packages — allowing the worm to spread further without manual intervention.

Worm-like Behavior

This design mimics biological worms: each new infection becomes a vector for further spread, creating exponential growth that’s particularly dangerous in large ecosystems like npm.

Why Supply Chain Attacks Are So Dangerous

Modern software development relies heavily on open-source packages, with developers importing thousands of external libraries into applications. This dependency model creates a “trusted but vulnerable” surface that attackers can exploit by injecting malicious code into dependencies that developers assume are safe.

Key risks include:

Wide reach: A single compromised package can impact thousands of applications and projects.
Silent propagation: Attackers can move through ecosystems undetected using stolen tokens.
Credential theft: Sensitive keys and secrets give attackers access to CI pipelines, production environments, and cloud accounts.

Because of these factors, supply chain compromises can lead to far greater damage than traditional endpoint vulnerabilities. They allow attackers to use legitimate developer workflows against organizations.

Current Observations and Containment

At the time of discovery, researchers reported:

No significant infections or reports of widespread compromise from this new npm package.
Limited downloads may have kept exposure relatively contained.
Early detection may have disrupted attack plans before broader activation.

This fortunate containment underscores the importance of real-time threat intelligence in catching attacks during early development or testing phases.

Security Recommendations — How to Protect Yourself

Developers, DevOps teams, and security engineers must treat software supply chain threats as high-priority risks. Here are recommended practices to mitigate similar attacks:

1. Audit npm Dependencies

Regularly review your project’s npm dependencies and check for unusual or infrequently maintained packages, especially those recently updated after long gaps.

2. Implement Integrity Tools

Use tools that validate package integrity and provenance, such as:

Reproducible builds
Signed packages
SHA-verified dependency manifests

3. Scan for Secrets Automatically

Run secret-scanning tools on source code repositories and CI pipelines to catch exposed tokens early.

4. Monitor for Unusual Publishing Activity

Automate alerts for unexpected updates from rarely changed packages or unusual behavioral patterns in dependency logs.

5. Enforce Multi-Factor Authentication (MFA)

Require strong MFA on all developer accounts with publish privileges to open registries like npm.

By implementing these measures, teams can both reduce their exposure and increase their chance of catching threats before they escalate.

Broader Implications for 2026

The discovery of this modified Shai-Hulud strain at the very end of 2025 suggests that supply chain threats will remain active and evolving in 2026. Security experts warn that attackers — empowered by insights from prior campaigns — may continue innovating with more sophisticated obfuscation, stealthier propagation, and deeper integration into developer tooling.

Unlike typical malware that targets endpoints, these supply chain attacks piggyback on trust and convenience — a combination that makes detection and pre-deployment mitigation notoriously difficult. Organizations must adapt by baking supply chain security into development lifecycles rather than treating it as an afterthought.

Final Thoughts: Early Detection Is Key

The spot of this modified Shai-Hulud strain — likely in testing — is a rare positive in the often reactive world of cybersecurity. Early visibility gives defenders an edge, allowing them to prepare and patch processes before attackers flip the switch on broader campaigns.

However, this event should not breed complacency. On the contrary, it serves as a strong reminder that software supply chains are active battlegrounds, and staying ahead requires vigilance, automation, and a deep understanding of both attacker techniques and defensive tooling.