Nearly 800 malicious packages were uploaded to the public npm registry in a recent supply-chain campaign that installs a cross-platform remote access trojan (RAT) and infostealer on developer systems running Windows, macOS or Linux.[1][4][10] Researchers say the cluster, first documented by OpenSourceMalware’s Paul McCarty, blends into the ecosystem using mass-generated, typo-adjacent names that resemble legitimate modules while ultimately delivering the same multi-OS malware family.[1][2][4]
The packages rely on what McCarty describes as “AI slop squatted” naming, using automated generation to crank out hundreds of lookalike identifiers that are easy to miss in dependency trees and lockfiles.[1][2] Analysis of samples shows a JavaScript-based loader that executes during installation, performs process.platform checks to identify the host operating system, and then pulls down platform-specific second-stage payloads from attacker-controlled infrastructure, providing both remote control and credential theft capabilities.[2][10] Some reporting ties the toolchain to a dropper tracked as WEL1DROPPER, used to bootstrap the RAT and infostealer components across Windows, macOS and Linux environments.[11]
While the campaign abuses npm as a distribution channel, it does not stem from a vulnerability in the registry itself, and there is currently no associated CVE or entry in CISA’s Known Exploited Vulnerabilities catalog.[2] Instead, the incident fits a growing pattern of adversaries publishing outright malicious packages at scale, which can be silently pulled into developer workstations, CI/CD runners and production environments whenever automated builds resolve the poisoned versions.[2][10] The malicious packages have been progressively removed from the registry as they are discovered, but researchers characterize the operation as active and in the wild at the time of disclosure, underscoring the need for retrospective exposure assessment.[1][2][10]
The npm campaign lands amid a surge in open-source supply-chain attacks that target JavaScript ecosystems specifically, including recent waves of malicious or compromised packages affecting node-gyp, popular libraries such as Axios, and scoped namespaces like @mastra and @redhat-cloud-services.[5][8][9][13] Separate research into malicious open-source components has documented a sharp rise in such activity, with one industry report finding a double-digit percentage increase in malicious packages across public registries year over year, reinforcing that these incidents are becoming routine rather than exceptional outliers.[14]
For organizations that routinely build from npm, the immediate priority is to identify whether any of the malicious packages were ever installed in developer environments, CI pipelines or production systems, using the indicators of compromise and package lists published by researchers as a starting point.[1][2][10] Security teams are being urged to review lockfiles and build logs for unexpected or unfamiliar package names, rotate credentials and tokens exposed on systems where suspect packages may have executed, and enhance telemetry around package installation events to flag anomalous network connections or script execution during npm install.[2]
Longer term, defenders are advised to tighten npm governance by pinning dependencies to vetted versions, mirroring critical packages into private registries, and applying allowlist-based controls for new third-party components introduced into builds.[2][5] Coupled with stronger maintainer hygiene and automated scanning for embedded malicious code, such controls can make it significantly harder for large-scale campaigns like the 800-package cluster to quietly land in enterprise software supply chains.[5][9][14]
References
- Nearly 800 Malicious npm Packages Deliver Cross- …
- 800 Malicious npm Packages Delivering Cross-Platform …
- Nearly 800 Malicious npm Packages Deliver Cross-Platform RAT …
- Node-gyp Supply Chain Compromise
- Axios NPM Supply Chain Compromise
- Mitigation And Protection…
- Nearly 800 Malicious npm Packages Distribute Cross-Platform RAT …
- “Nearly 800 Malicious npm Packages Deliver Cross-Platform RAT …
- RHSB-2026-006 Supply chain compromise of @redhat-cloud …
- ReversingLabs Report: 73% Rise in Malicious Open Source | ReversingLabs
