Advisory

MAL-2026-20044

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-team/wppconnect (npm)

Details

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

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-team/wppconnect

npm · All systems

Affected

  • Versions: 2.4.1

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