noxleysnpm
noxleys is a confirmed malicious npm package (MAL-2026-13831) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.1.1…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in noxleys (npm)
What this malware does
This package is a fork of the Baileys WhatsApp library that wires an undocumented routine into the connection lifecycle. On every WhatsApp connection.update where connection === 'open', after a 30-second delay the library fetches a JSON list of channel IDs from a hardcoded, author-controlled GitHub raw URL on a mutable branch (https://raw.githubusercontent.com/noxXza/data/refs/heads/main/noxXza.json) and, for each ID, invokes newsletterFollow followed by newsletterMute on the installer's authenticated WhatsApp account, with randomized shuffling and delay jitter. The behavior is not disclosed in the package README, is not gated behind an opt-in flag, and uses the installer's own WhatsApp identity to perform actions the caller did not request. Because the channel-ID list is served from a mutable main branch, the set of followed accounts can be changed by the author at any time without a package release. Additional helpers in generics.js (hwaifu(), fetchLatestBaileysVersion()) also fetch JSON from mutable-branch author-controlled GitHub raw URLs (raw.githubusercontent.com/ramadanny/...), but only as data (no code eval) and not auto-invoked at import/install time. No credential theft, environment scraping, install-time code execution, dropper behavior, or backdoor mechanism is present.
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 noxleys (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging noxleys across your stack and pipelines.
If you installed it — respond
noxleys 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 noxleys 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 noxleys 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 noxleys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.