Loading story…
The Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent advisory following the discovery of a widespread supply chain attack targeting the npm package ecosystem, known as the Shai-Hulud intrusion. Security researchers from StepSecurity identified that over 500 npm packages were compromised with self-replicating malware, significantly increasing the risk to organizations relying on open-source dependencies. The attack involved the injection of malicious code into popular packages, including the Nx build system and its related plugins, which are widely used for managing monorepos and automating development workflows. The malicious code, developed using a large language model according to Palo Alto Networks, was designed to execute immediately after package installation via a post-install hook, specifically targeting non-Windows systems. Once executed, the malware, named telemetry.js, collected sensitive host information, cryptocurrency wallets, and development credentials from affected developer machines. The stolen data was then triple-base64 encoded and exfiltrated to a public GitHub repository created using compromised GitHub tokens, under the name s1ngularity-repository. In addition to data theft, the malware attempted to disrupt developer operations by causing new terminal sessions to trigger immediate system shutdowns, resulting in denial-of-service conditions. CISA has recommended that all organizations using npm packages conduct immediate dependency reviews and thoroughly examine cached versions of affected dependencies to prevent further compromise. GitHub responded by removing the more than 500 impacted packages and implementing a ban on new uploads containing Shai-Hulud indicators of compromise. Security teams are also advised to rotate developer account credentials and enforce phishing-resistant multi-factor authentication to mitigate the risk of further account takeovers. The affected Nx packages include nx/devkit, nx/enterprise, nx/eslint, nx/js, nx/key, nx/node, and nx/workspace, with specific versions listed as vulnerable. The attack highlights the growing sophistication of supply chain threats, particularly those leveraging AI-generated code to evade detection and maximize impact. Organizations are urged to remain vigilant, update their security controls, and monitor for signs of compromise related to the Shai-Hulud malware. The incident underscores the critical importance of securing the software development lifecycle and maintaining robust monitoring of third-party dependencies. CISA's alert emphasizes the need for immediate action to prevent further exploitation and data loss. The coordinated response from security vendors, government agencies, and the open-source community demonstrates the seriousness of the threat and the necessity for ongoing vigilance in the face of evolving supply chain attacks.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
Subsequent reporting linked the compromise to the 'Shai-Hulud' attack and stated that roughly 800 private repositories had been made public, showing broader downstream impact from the stolen credentials and package compromise.
U.S. cybersecurity authorities and CIS published advisories warning that the Nx package issue represented an extensive supply-chain compromise and urged organizations to immediately check dependencies, rotate exposed credentials, and assess affected environments.
A supply-chain compromise involving the Nx build system package enabled sensitive data exfiltration from developer and CI/CD environments, including tokens and other secrets that could be used to access source code repositories.
3 references tracked. Mallory keeps watching after this page renders.
securitysenses.com
Open sourcescworld.com
Open sourcecisecurity.org
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 large-scale supply chain attack has targeted the Node Package Manager (NPM) ecosystem, compromising hundreds of widely used JavaScript packages and threatening the security of software development pipelines globally. In mid-September, cybersecurity researchers identified a self-propagating malware dubbed "Shai-Hulud," which was distributed through trojanized NPM packages, including some with millions of weekly downloads and high-profile packages such as those from CrowdStrike. The attack leveraged a malicious "bundle.js" script that downloaded and executed TruffleHog, a legitimate credential scanner, to harvest developer and CI/CD tokens, cloud service credentials, and environment variables from compromised systems. The stolen credentials were exfiltrated via hard-coded webhooks and GitHub Actions workflows, enabling the attacker to further propagate the malware and gain unauthorized access to sensitive resources. The campaign affected both Windows and Linux systems, increasing its reach and impact across diverse development environments. Sysdig reported that the attack on September 15 involved approximately 200 compromised packages, including @ctrl/tinycolor, and was linked to an attacker who had previously targeted Nx packages in late August. The worm not only stole secrets but also published them publicly on GitHub and attempted to make victim repositories public, amplifying the risk of further compromise. Earlier in the month, other popular packages such as chalk, debug, and duck were also compromised following a successful spear phishing attack against a maintainer, with the attacker seeking to redirect cryptocurrency payments. NPM responded by removing the malicious package versions, but users were required to update or revert to secure versions to mitigate the risk. Sysdig provided same-day threat intelligence and detection capabilities to its customers, including open source Falco rules to identify and respond to the threat. The attack demonstrated the vulnerability of even the most trusted and widely used open source packages, highlighting the importance of continuous monitoring and rapid response in the software supply chain. Security researchers and vendors emphasized the need for organizations to scan their environments for known malicious packages, such as dist.fezbox.cjs, and to review logs for signs of credential exfiltration. The incident underscored the evolving tactics of threat actors targeting developer ecosystems, using advanced techniques to automate propagation and maximize impact. Organizations relying on NPM packages and CI/CD pipelines were urged to remain vigilant, update dependencies promptly, and leverage threat intelligence resources to defend against similar attacks. The Shai-Hulud campaign remains an evolving threat, with ongoing analysis and mitigation efforts by the security community. This incident serves as a stark reminder that popularity and trust in open source packages do not guarantee safety, and proactive security measures are essential to protect software supply chains from compromise.
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
A major supply chain attack targeted the npm ecosystem in September 2025, where an infostealer with worm-like characteristics, dubbed **Shai-Hulud**, compromised over 500 npm packages. The attack leveraged a previous compromise of the `s1ngularity/nx` project, exploiting CI/CD pipeline credentials and propagating through both direct and indirect dependencies. Security researchers confirmed that attackers exfiltrated GitHub and npm tokens, enabling them to inject malicious code into widely used packages and potentially access internal networks, move laterally, or tamper with software releases. The incident highlighted the persistent risks associated with CI/CD pipeline security, as attackers exploited overlooked access to secrets such as API keys and deployment tokens. The scale of the attack forced engineering and security teams worldwide to spend significant resources cleaning compromised environments and assessing exposure, even though the direct financial impact was limited. The event underscored the need for enhanced runtime security monitoring, such as eBPF-based sensors, and stricter controls on package publishing and consumption to defend against similar threats in the future.
Jun 29, 2026