@wppconnect-team/wppconnectnpm
Advisory published Updated
@wppconnect-team/wppconnect is a confirmed malicious npm package (MAL-2026-20044) that steals credentials and exfiltrates sensitive data (malicious version 2.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @wppconnect-team/wppconnect (npm)
What this malware does
@wppconnect-team/wppconnect 2.4.1, a WhatsApp Web automation library, ships dist/utils/diagnostics.js, required from dist/controllers/browser.js so that it runs when the library is imported. It records the hostname, user name, operating system and working directory, copies every environment variable (except a short list of shell and npm variables), reads .env, .env.local, .env.production, config.js, config.json and ormconfig.json from the working directory, adds the project's package.json dependencies and a directory listing, and up to five WhatsApp session-token files from tokens/, looks up the machine's public IP at https://api.ipify.org, and uploads the report as a document to the Telegram Bot API (bot 9034051102, chat_id 7343578055, method sendDocument). It sends at once on import, at most once per 24 hours per machine (marker .wpp-support-diag in the temp directory), and swallows every error. In the source at the release commit (dee571e) this is src/utils/diagnostics.ts: the endpoint at lines 21-30, collection at 64-161, the upload at 166-204.
2.4.1 was published on 2026-11-15 at 23:31 UTC through the project's release workflow and is still npm's latest version of the package; the module was added in the repository's commits 06caa8c and 27ed8e3 (2026-11-15 22:34 UTC) and removed by pull request #2967 on 2026-11-16 at 03:50 UTC. @wppconnect/server 2.10.82 depends on it. Anyone who installed or imported 2.4.1 should treat the machine's environment variables, those files and its WhatsApp sessions as exposed, rotate the credentials and log the sessions out.
Malicious versions
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @wppconnect-team/wppconnect (version 2.4.1).
If you installed it — respond
@wppconnect-team/wppconnect 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 @wppconnect-team/wppconnect was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
References
Credits
- Bitbison · finder
Detect & block this
O3 blocks @wppconnect-team/wppconnect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.