wellnpmnpm
wellnpm is a confirmed malicious npm package (MAL-2026-6501) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.9, 2.0.10, 2.0.11…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in wellnpm (npm)
What this malware does
[email protected] ships a 24MB ELF binary named launch which is the XMRig Monero miner (RandomX, cn/upx2, ghostrider algorithm strings, libuv/OpenSSL linkage, hashvault pool references). package.json declares "main": "launch" and "scripts.start": "./launch", so running npm start on this package immediately launches the miner. A bundled config.json is pre-configured against pool.hashvault.pro:80 with the hardcoded recipient wallet 4AUTfJGTvT8A98PSE99EunfrnUbkWe9vU3FN3qsABQLP5aPKQuvWS5sCaD9WaXFQUqNtDLb9dcxiBgJiWCfjvDXp5ptWDYG, so all hashrate from victim machines is credited to the author. A second scripts.deploy script targets Android Termux: it moves libuv.so into /data/data/com.termux/files/usr/lib, chmod+x's the xmr and edit shell wrappers, and copies them into /data/data/com.termux/files/usr/bin so the miner becomes a persistent, PATH-resolvable command in the user's Termux environment. The wrappers themselves are one-liners that cd node_modules/wellnpm && npm start. README does not mention mining; metadata is placeholder (author: Your Name <wellenterprise81.gmail.com>, description: A brief description of your package). This is a cryptojacking dropper masquerading as an npm module.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wellnpm (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wellnpm across your stack and pipelines.
If you installed it — respond
wellnpm is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wellnpm was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks wellnpm before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks wellnpm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.