Advisory

MAL-2026-20043

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in @wppconnect/server (npm)

Details

@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.

Severity

Not rated by the source.

Dates

Published
2026-11-16 04:10 UTC
Modified
2026-11-17 05:45 UTC

Affected packages and fixes

@wppconnect/server

npm · All systems

Affected

  • Versions: 2.10.82

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences