The malware attack on the npm repository, which distributes open-source packages for the widely used programming language JavaScript, is far more severe than feared: A malware worm introduced into the system has now infected over 180 software packages.
At least 180 open-source packages distributed via the npm repository for the JavaScript programming language are infected by a self-replicating worm. The malware steals credentials and identifies repositories of other open-source packages, infiltrating them and further spreading throughout the npm ecosystem.
Cybersecurity experts have identified a new wave of malware being distributed through the npm package registry. Although the malware being spread this time is of a different nature, it is believed to stem from the same attack on the repository discovered last week, which distributes open-source software packages for the JavaScript programming language.
"The compromised versions contain a function (NpmModule.updatePackage) that downloads a package tarball, modifies the package.json file, inserts a local script (bundle.js), repacks the archive, and republishes it, enabling an automatic trojanization of downstream packages," states a blog post by Socket, which also highlighted the first malware attack. Such self-replicating malware, also known as a worm, can rapidly spread further through the infected repository.
Other security researchers have also consistently reported on the malware. Unlike last week’s attack, however, the worm does not deploy hidden cryptocurrency mining software but is potentially much more dangerous: it specifically targets and exfiltrates sensitive credentials from infected systems. The worm is spreading rapidly: while initial reports mentioned 40 affected packages, the majority now believe over 180 packages have been compromised; some estimates fear it could already be over 500..
Operation of the Malware
The Software Supply Chain Worm, which automatically replicates itself via dependent packages, operates as follows: malicious code is executed when compromised packages are installed. On the infected system, the injected malware scans local systems for secret tokens (e.g., GITHUB_TOKEN, AWS_ACCESS_KEY_ID) and exfiltrates them via webhooks to external servers. The attack affects both Windows and Linux systems.
Subsequently, a file named bundle.js injected into the infected packages uses legitimate tools like TruffleHog to locate credentials for other packages distributed via the npm repository. GitHub repositories are then created or modified, workflows are injected, and new compromised versions of other packages are automatically published – including malicious code. Further insights into the malware's operation are provided by the StepSecurity blog.
The attackers use the repository "Shai-Hulud," named after the legendary sandworms from the science fiction epic Dune. The name is more than just a pop culture reference – the analogy to a worm burrowing through the ecosystem and spreading uncontrollably fits alarmingly well.
Among the affected packages are those from the @ctrl ecosystem, the NativeScript community, as well as numerous projects related to CrowdStrike. Particularly concerning: Some of these packages, such as @ctrl/tinycolor, achieve millions of downloads weekly.
Connection to the Recent Attack Seems Likely
According to ReversingLabs, the attack likely began with the package rxnt-authentication, which was published on September 14. The associated account, techsupportrxnt, is currently considered "Patient Zero." It remains unclear exactly how the account was compromised – phishing or a faulty GitHub workflow configuration are considered possible causes.
CrowdStrike responded immediately and removed the affected packages from the registry. According to their own statement, the platform itself was not affected. Internal keys have been rotated, and a thorough investigation is underway in collaboration with the npm team.
The impact of the campaign is far-reaching: An analysis of the stolen data, according to GitGuardian, has already revealed at least 278 compromised secrets, including 188 that were leaked directly through manipulated GitHub workflows. Security researchers are calling it a "cascade compromise" of the npm ecosystem.
Developers are strongly advised to check their environments for affected package versions, immediately rotate tokens and credentials, and review all build processes. Projects that perform automatic deployments and publishing without adequately isolating secrets are particularly at risk.
Security Researchers Urge Greater Awareness in the Use of Open-Source Packages
In the long term, the incident once again raises the question of the resilience of open-source infrastructures. The close integration of developer accounts, CI/CD pipelines, and package managers requires not only technological protective measures but also a higher level of awareness – particularly in professional DevOps and security teams.
Date: 08.12.2025
Naturally, we always handle your personal data responsibly. Any personal data we receive from you is processed in accordance with applicable data protection legislation. For detailed information please see our privacy policy.
Consent to the use of data for promotional purposes
I hereby consent to Vogel Communications Group GmbH & Co. KG, Max-Planck-Str. 7-9, 97082 Würzburg including any affiliated companies according to §§ 15 et seq. AktG (hereafter: Vogel Communications Group) using my e-mail address to send editorial newsletters. A list of all affiliated companies can be found here
Newsletter content may include all products and services of any companies mentioned above, including for example specialist journals and books, events and fairs as well as event-related products and services, print and digital media offers and services such as additional (editorial) newsletters, raffles, lead campaigns, market research both online and offline, specialist webportals and e-learning offers. In case my personal telephone number has also been collected, it may be used for offers of aforementioned products, for services of the companies mentioned above, and market research purposes.
Additionally, my consent also includes the processing of my email address and telephone number for data matching for marketing purposes with select advertising partners such as LinkedIn, Google, and Meta. For this, Vogel Communications Group may transmit said data in hashed form to the advertising partners who then use said data to determine whether I am also a member of the mentioned advertising partner portals. Vogel Communications Group uses this feature for the purposes of re-targeting (up-selling, cross-selling, and customer loyalty), generating so-called look-alike audiences for acquisition of new customers, and as basis for exclusion for on-going advertising campaigns. Further information can be found in section “data matching for marketing purposes”.
In case I access protected data on Internet portals of Vogel Communications Group including any affiliated companies according to §§ 15 et seq. AktG, I need to provide further data in order to register for the access to such content. In return for this free access to editorial content, my data may be used in accordance with this consent for the purposes stated here. This does not apply to data matching for marketing purposes.
Right of revocation
I understand that I can revoke my consent at will. My revocation does not change the lawfulness of data processing that was conducted based on my consent leading up to my revocation. One option to declare my revocation is to use the contact form found at https://contact.vogel.de. In case I no longer wish to receive certain newsletters, I have subscribed to, I can also click on the unsubscribe link included at the end of a newsletter. Further information regarding my right of revocation and the implementation of it as well as the consequences of my revocation can be found in the data protection declaration, section editorial newsletter.
The following packages have been clearly identified as compromised by Socket: