Spectra Assure Free Trial
Get your 14-day free trial of Spectra Assure for Software Supply Chain Security
Get Free TrialMore about Spectra Assure Free TrialDespite a broader range, the Mini Shai Hulud campaign’s objectives are consistent with earlier outbreaks. Attackers compromise developer environments with the goal of stealing credentials, and abusing trusted publishing workflows to spread further within compromised environments.
While most of the affected packages are on the npm open-source repository, the ripple effects of the attack stretch far beyond npm. On Monday, the Guardrails AI project acknowledged that malicious activity linked to the campaign affected components within its ecosystem as well.
The worm-like behavior of the campaign hinges on harvesting developer and automation secrets from infected systems and then using those credentials to publish additional malicious packages, The Hacker News reported.
That behavior closely mirrors the original Shai-Hulud worm documented by ReversingLabs researchers in 2025. RL researchers observed how Shai-Hulud systematically harvested npm tokens, GitHub credentials, and cloud provider secrets from compromised developer environments using tools like TruffleHog. The malware then leveraged those credentials to tamper with additional packages and repositories, effectively turning the software supply chain itself into a propagation mechanism.
As RL explained in its Shai-Hulud FAQ and analysis, the campaign represents a dangerous evolution in open-source malware. Rather than relying on developers to mistakenly install typo-squatted packages, the attackers compromised legitimate and highly trusted packages directly.
The latest Mini Shai-Hulud activity reinforces a broader trend RL has documented in recent Software Supply Chain Security Reports: attackers are increasingly targeting the infrastructure and trust relationships that underpin open-source ecosystems rather than simply exploiting software vulnerabilities. RL’s 2026 report notes that npm accounted for nearly 90% of detected open-source malware in 2025 and highlights how campaigns like Shai-Hulud weaponized stolen credentials to spread at scale.
The campaign also demonstrates how exposed development secrets continue to fuel software supply chain attacks. RL researchers have repeatedly shown that leaked npm tokens, GitHub personal access tokens, cloud credentials, and CI/CD secrets remain widely available across open-source ecosystems.
For software teams and developers whose environments may have touched any compromised package versions, the response should be immediate and aggressive:
Organizations should also review publishing workflows, implement short-lived credentials where possible, enforce MFA across package registries and source control platforms, and continuously monitor software artifacts for tampering and unauthorized changes.
The RL threat research team is continuing to monitor open-source registries as this campaign evolves.



The annual cybersecurity conference focused on frontier AI agents — and what they mean for cyber. Here are three key takeaways.

Researchers built a worm that reasons about hosts it infects, and the open-weight models powering it sit outside AI-provider safety controls.

While prompt injection and data disclosure remain concerns, excessive agency climbed the list — not surprising with recent security incidents.