Malicious wppconnect 2.4.1 and @wppconnect/server 2.10.82 npm releases steal secrets and WhatsApp sessions via Telegram
Two malicious npm releases, wppconnect 2.4.1 and @wppconnect/server 2.10.82, were published through the project's own GitHub Actions trusted-publishing workflow. They steal environment variables, config files and WhatsApp session tokens, then upload them to a Telegram bot. The payload runs on any require()/import of the library or on server start. Stolen session tokens let an attacker take over a WhatsApp account without a QR scan. npm has since deprecated both versions and moved latest back to 2.4.0 and 2.10.81. npm counted 155 downloads of 2.4.1 in its last 7-day window, and 2.10.82 has no figure yet. This record rests on one source (safedep.io). No vendor advisory, CVE or attribution was researched or reported.
Detalhes técnicos
- Neither package has install scripts. Each release adds one
requirethat loads an "environment diagnostics" module (utils/diagnosticsin the library,util/diagnosticsin the server). - The payload runs at most once a day per machine, tracked in
<tmpdir>/.wpp-support-diag. It collects host info and environment variables with 3 to 499 character values. It also reads the first 12,000 bytes of.env,.env.local,.env.production,config.js,config.jsonandormconfig.json. It lists dependencies, scripts and the first 60 files, and reads up to 5 session files from./tokens/. - It looks up the public IP via api.ipify.org and uploads a text file named
<hostname>_<YYYYMMDD-HHMMSS>.txtthrough the TelegramsendDocumentAPI. The Telegram chat ID is 7343578055 and the bot ID is 9034051102. - The server variant base64-encodes the endpoint and adds a random 30s to 4min delay. It skips CI runners, research sandboxes, hostnames such as sandbox/test/runner, and proxies containing "mitm". Its inline source map still holds the library's bot token.
- The git history was rewritten. The npm releases were built from unsigned payload commits 06caa8c and 27ed8e3 and release commit dee571e, which no branch or tag contains. The v2.4.1 tag and master point to a look-alike history (63956bf, 43ef1dc) that omits the payload, so reviewing the GitHub source would not reveal the stealer. The server was changed in commit bdddf54.
- Timeline: payload commits 15 Nov 22:34. 2.4.1 published 15 Nov 23:31. 2.10.82 published 16 Nov 03:09. Both deprecated around 08:00 on 16 Nov.
Remediação
The article gives no explicit steps. Defenders should check for wppconnect 2.4.1 and @wppconnect/server 2.10.82 and move to 2.4.0 and 2.10.81 or later clean releases. They should rotate secrets exposed on affected machines and invalidate WhatsApp sessions. They should also treat unusual traffic to api.telegram.org as suspect.
Linha do tempo
-
Malicious wppconnect 2.4.1 and @wppconnect/server 2.10.82 npm releases steal secrets and WhatsApp sessions via Telegram
ler a análise desta fonte ocultar
Two malicious npm releases, wppconnect 2.4.1 and @wppconnect/server 2.10.82, were published through the project's own GitHub Actions trusted-publishing workflow. They steal environment variables, config files and WhatsApp session tokens, then upload them to a Telegram bot. The payload runs on any
require()/import of the library or on server start. Stolen session tokens let an attacker take over a WhatsApp account without a QR scan. npm has since deprecated both versions and movedlatestback to 2.4.0 and 2.10.81. npm counted 155 downloads of 2.4.1 in its last 7-day window, and 2.10.82 has no figure yet. This record rests on one source (safedep.io). No vendor advisory, CVE or attribution was researched or reported.Technical Details
- Neither package has install scripts. Each release adds one
requirethat loads an "environment diagnostics" module (utils/diagnosticsin the library,util/diagnosticsin the server). - The payload runs at most once a day per machine, tracked in
<tmpdir>/.wpp-support-diag. It collects host info and environment variables with 3 to 499 character values. It also reads the first 12,000 bytes of.env,.env.local,.env.production,config.js,config.jsonandormconfig.json. It lists dependencies, scripts and the first 60 files, and reads up to 5 session files from./tokens/. - It looks up the public IP via api.ipify.org and uploads a text file named
<hostname>_<YYYYMMDD-HHMMSS>.txtthrough the TelegramsendDocumentAPI. The Telegram chat ID is 7343578055 and the bot ID is 9034051102. - The server variant base64-encodes the endpoint and adds a random 30s to 4min delay. It skips CI runners, research sandboxes, hostnames such as sandbox/test/runner, and proxies containing "mitm". Its inline source map still holds the library's bot token.
- The git history was rewritten. The npm releases were built from unsigned payload commits 06caa8c and 27ed8e3 and release commit dee571e, which no branch or tag contains. The v2.4.1 tag and master point to a look-alike history (63956bf, 43ef1dc) that omits the payload, so reviewing the GitHub source would not reveal the stealer. The server was changed in commit bdddf54.
- Timeline: payload commits 15 Nov 22:34. 2.4.1 published 15 Nov 23:31. 2.10.82 published 16 Nov 03:09. Both deprecated around 08:00 on 16 Nov.
Remediation
The article gives no explicit steps. Defenders should check for wppconnect 2.4.1 and @wppconnect/server 2.10.82 and move to 2.4.0 and 2.10.81 or later clean releases. They should rotate secrets exposed on affected machines and invalidate WhatsApp sessions. They should also treat unusual traffic to api.telegram.org as suspect.
- Neither package has install scripts. Each release adds one