NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@wppconnect/servernpm

Advisory published Updated

@wppconnect/server is a confirmed malicious npm package (MAL-2026-20043) that steals credentials and exfiltrates sensitive data (malicious version 2.10.82). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wppconnect/server (npm)

MAL-2026-20043
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wppconnect/server

What this malware does

@wppconnect/server 2.10.82, a REST server for WhatsApp automation, ships dist/util/diagnostics.js, loaded unconditionally on server start by dist/server.js:18 (2.10.81's dist/server.js does not load it). It collects every environment variable, the files .env, .env.local, .env.production, config.js, config.json and ormconfig.json from the working directory, and the WhatsApp session-token files under tokens/ and wppconnect_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 waits a random 30 to 240 seconds before sending, sends at most once per 24 hours per machine (a marker file in the temp directory), and does nothing on machines it identifies as CI or a sandbox (CI, GITHUB_ACTIONS and RUNNER_* variables, sandbox-like hostnames). The Telegram endpoint is assembled from base64 parts (dist/util/diagnostics.js:27-33); collection is at lines 113-207 and the upload at 196-233. The same module reaches the server through its dependency @wppconnect-team/wppconnect 2.4.1, which runs it on import.

2.10.82 was published on 2026-11-16 at 03:09 UTC through the project's release workflow; the source line was added in the repository's commit bdddf54 (2026-11-16 02:43 UTC) and removed by pull request #2733 at 03:44 UTC, but 2.10.82 is still served by npm. Anyone who installed or started 2.10.82 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

1 flagged
2.10.82

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @wppconnect/server (version 2.10.82).

  2. If you installed it — respond

    @wppconnect/server 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.

  3. Did it already run?

    If @wppconnect/server 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

No. @wppconnect/server on npm has been identified as a malicious package (version 2.10.82 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Bitbison · finder

Detect & block this

O3 blocks @wppconnect/server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@wppconnect/server (npm) malicious package — MAL-2026-20043 | O3 Security