Loading story…
A self-propagating worm named Shai Hulud has compromised hundreds of npm packages, including high-profile ones from CrowdStrike and others, by leveraging compromised maintainer accounts. The malware harvests secrets from CI/CD environments and cloud metadata, exfiltrates them via GitHub repositories and malicious workflows, and automatically republishes itself to other packages. This incident marks a significant escalation in open source supply chain attacks, with rapid propagation and widespread exposure of sensitive data.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
7 events from the most recent confirmed update back to the earliest known activity.
JFrog reported an active 2026-05-19 wave of the Shai-Hulud supply-chain campaign that compromised 325 legitimate npm packages, mainly in the @antv ecosystem, and also identified related compromises in the PyPI package durabletask and npm package @cap-js/openapi. The report described new delivery and propagation details, including optionalDependencies-based payload fetching, Linux-focused PyPI malware with AWS Systems Manager and Kubernetes lateral movement, and warned that revoking stolen GitHub tokens can trigger destructive dead-man-switch behavior.
A local Python IOC scanner for Mini Shai-Hulud and Shai-Hulud npm supply-chain compromise indicators was published on GitHub. The tool checks for malicious files, hashes, compromised package versions, suspicious npm scripts, obfuscated payloads, stored npm tokens, and other local artifacts, with the bundled IOC feed reviewed on 2026-05-11.
Elastic Security Labs published an updated response to the Shai-Hulud Worm 2.0 npm supply-chain compromise. The publication added another vendor-backed defender resource covering the campaign and response guidance.
A GitHub repository published KQL-based Microsoft Defender hunting and detection guidance for the Shai-Hulud worm. This added publicly available defender-focused technical content for identifying related activity in enterprise telemetry.
Trend Micro published research on the evolved Shai-Hulud 2.0 campaign, describing its targeting of cloud and developer ecosystems. The report represents an additional public technical analysis of the malware and its operational scope beyond the earlier GitLab disclosure.
GitLab's Vulnerability Research team reported an active large-scale npm supply-chain campaign using an evolved Shai-Hulud variant that spreads by republishing infected packages with stolen npm tokens. GitLab also published indicators of compromise and detection guidance, describing credential theft, GitHub-based exfiltration, possible GitHub Actions runner persistence, and a destructive dead man's switch.
Initial story creation
22 references tracked. Mallory keeps watching after this page renders.
research.jfrog.com
Open sourcegithub.com
Open sourceelastic.co
Open sourcegithub.com
Open sourcetrendmicro.com
Open sourceapiiro.com
Open sourceaikido.dev
Open sourceupwind.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A self-replicating worm known as Shai-Hulud was used to compromise over 500 npm packages, enabling attackers to steal sensitive credentials such as GitHub Personal Access Tokens and API keys for major cloud services. The malware spread by injecting itself into additional packages, leveraging stolen credentials to propagate further. GitHub responded by removing the compromised packages from the npm registry and working with open source maintainers to contain the attack. The Cybersecurity and Infrastructure Security Agency (CISA) issued a warning urging organizations to review their software for signs of compromise, rotate developer credentials, and monitor for anomalous network activity. The incident highlights the risks of supply chain attacks in the open source ecosystem and the importance of rapid response and credential hygiene.
Jun 29, 2026A self-replicating worm dubbed 'Shai-hulud' has compromised hundreds of npm packages, including widely used libraries like @ctrl/tinycolor and several CrowdStrike packages. The malware steals developer credentials, exfiltrates secrets, and spreads automatically by republishing trojanized packages, persisting via GitHub Actions workflows. Organizations are urged to audit environments, rotate all credentials, and remove compromised packages immediately.
Jun 29, 2026
A series of sophisticated supply chain attacks targeted the npm JavaScript ecosystem, culminating in the discovery of the Shai-Hulud worm, which demonstrated the potential for self-propagating malware within open-source package registries. Attackers initially compromised credentials of trusted maintainers through social engineering, leading to the injection of malicious payloads into high-profile packages such as Chalk, Debug, ansi-styles, and supports-color. These packages, collectively downloaded billions of times weekly, were updated with malware designed to intercept cryptocurrency activity and manipulate transactions for the attackers' benefit. The rapid response from maintainers and npm limited the exposure window, but any systems or build pipelines that fetched the compromised packages during this period were at risk. Shortly after, the Shai-Hulud worm emerged, marking one of the first large-scale, self-replicating malware outbreaks in the npm supply chain. The worm exploited compromised developer accounts to inject malicious code into all packages maintained by those accounts, leveraging package interdependencies to spread autonomously. Upon installation, the infected packages executed a postinstall script that deployed a malicious bundle.js, which searched for and harvested sensitive credentials, including npm tokens, GitHub personal access tokens, and cloud provider credentials such as AWS and GCP. The worm used tools like TruffleHog to identify and exfiltrate over 800 types of secrets, sending them to attacker-controlled GitHub repositories. In some cases, the worm published new malicious package versions using stolen npm tokens, further amplifying its reach. The attacks highlighted the dangers of install scripts in npm packages and the limitations of simply banning such scripts, as attackers continually adapt their methods. Security experts emphasized the need for a mindset shift among developers, urging them to understand the risks inherent in running npm install and to adopt smarter dependency management practices. The incidents also exposed the risks posed by misconfigured GitHub Actions and the weaponization of AI tools to scan for secrets, expanding the attack surface. While the immediate crisis was contained, the events underscored the critical importance of rapid incident response, credential hygiene, and robust supply chain security measures. Organizations were advised to audit their dependencies, monitor for suspicious package updates, and implement automated secret scanning in their CI/CD pipelines. The Shai-Hulud outbreak served as a wake-up call for the open-source community, demonstrating that even widely trusted packages and maintainers can become vectors for large-scale compromise.
Jun 29, 2026