Just weeks after the devastating “Second Coming” campaign crippled thousands of development environments, the threat actor behind the Shai-Hulud worm has returned. Security researchers at Aikido have detected a new, evolved strain of the malware dubbed “The Golden Path,” signaling that the most aggressive supply chain predator in the npm ecosystem is far from finished.
This latest iteration was first spotted on over the weekend, embedded within the package @vietmoney/react-big-calendar. While the initial discovery suggests the attackers may still be in a “testing” phase with limited spread, the technical refinements found in the code point to a more resilient and cross-platform threat.
Evolution of a Predator
Shai-Hulud has long utilized a Dune-inspired theatrical flair, but its latest evolution suggests a shift in branding. In this new wave, stolen data is exfiltrated to GitHub repositories featuring a cryptic new description: “Goldox-T3chs: Only Happy Girl.
Technically, “The Golden Path” is a significant upgrade. Earlier versions of the worm struggled with Windows environments when attempting to self-propagate using the bun runtime. The new strain specifically addresses this, implementing cross-platform publishing capabilities that ensure the worm can spread regardless of the victim’s operating system.
Researchers also noted a shift in file nomenclature—the malware now operates via bun_installer.js and environment_source.js—and features improved error handling for TruffleHog, the secret-scanning tool the worm uses to harvest AWS, GCP, and Azure credentials. By refining its timeout logic, the malware is now less likely to crash during high-latency scans, making its “smash-and-grab” operations more reliable.
A Legacy of Disruption
This isn’t Shai-Hulud’s first rodeo. The group first made headlines in September 2025 when a massive campaign hit over 500 npm packages, including those belonging to cybersecurity giant CrowdStrike.
Read: CrowdStrike Among Those Hit in NPM Attack Campaign
That initial strike was historically significant, resulting in the theft of an estimated $50 million in cryptocurrency and proving that even the most security-conscious organizations are vulnerable to upstream dependency hijacking.
In November, the “Second Coming” wave escalated the stakes by introducing a “dead man’s switch”—a destructive payload designed to wipe a user’s home directory if the malware detected it had been cut off from its command-and-control (C2) servers.
Read: New Shai-Hulud Attack Hits Nearly 500 npm Packages with 100+ Million Downloads
The Supply Chain Standoff
The return of Shai-Hulud underscores a grim reality for modern DevOps: trust is a liability. By targeting the preinstall phase of npm packages, the malware executes before a developer even realizes a package is malicious.
“The differences in the code suggests that this was obfuscated again from original source, not modified in place,” Aikido researchers noted. “This makes it highly unlikely to be a copy-cat, but was made by somebody who had access to the original source code for the worm.”
Relying on npm’s default security is no longer sufficient. Organizations are urged to adopt “Trusted Publishing,” enforce strict lockfile integrity, and utilize package-aging tools that block the installation of brand-new, unvetted releases. In the world of Shai-Hulud, the only way to survive the desert is to stop trusting the ground beneath your feet.
