@wppconnect-team/wppconnect 2.4.1 uploads environment variables, project config files and WhatsApp session tokens to a Telegram chat when an app imports it.
The release went out through the project's own npm pipeline on 15 November 2026. Version 2.4.0 does not load the added file, and npm has now removed 2.4.1 from the registry.
What happened
Version 2.4.1 added dist/utils/diagnostics.js, and dist/controllers/browser.js loads it on import.
- It reads every environment variable except a short list of shell and npm names.
- It reads
.env,.env.local,.env.production,config.js,config.jsonandormconfig.jsonfrom the working directory. - It reads up to five JSON session files from the
tokensfolder. - It looks up the public IP address through
api.ipify.org. - It uploads the report to Telegram chat
7343578055, at most once every 24 hours.
Flatt Security dates the npm release to 23:31 UTC on 15 November 2026. Flatt Security does not say how the attacker got write access.
Affected versions
@wppconnect-team/wppconnect 2.4.1@wppconnect/server 2.10.82carries a related module. See the WPPConnect Server page.- Flatt Security names
2.4.0as the safe version. - npm removed
2.4.1from the registry. The current latest release is2.4.6, and a GitHub advisory dated 21 November 2026 lists2.4.1as malicious.
Indicators of compromise
dist/utils/diagnostics.js.wpp-support-diagin the temporary directoryapi.telegram.orguploads to chat7343578055api.ipify.org
How to check
List the installed version without running it.
npm ls @wppconnect-team/wppconnect
Look for the marker file in the temporary directory.
ls -la "${TMPDIR:-/tmp}"/.wpp-support-diag
What to do now
- Pin
@wppconnect-team/wppconnectto2.4.0and reinstall from a clean lockfile. - Rotate every secret in the environment and config files from a clean computer.
- Log out the WhatsApp sessions in the
tokensfolder and pair them again. - Search network logs for traffic to
api.telegram.orgfrom the app host.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `@wppconnect-team/wppconnect` 2.4.1. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
@wppconnect-team/wppconnect 2.4.1
When an app loads the library, it sends the app's secrets, config files and WhatsApp logins to a Telegram chat.
No security team? See who reads the alert.
Frequently asked questions
Does npm install alone run the code?
No. The code runs when an app imports or requires the library. Flatt Security reports no install script.
Sources
Send this page to the person who looks after AI at your company.