npm

The WPPConnect npm Supply Chain Attack

Updated 21 Nov 2026 · Incident date 15 Nov 2026

@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.json and ormconfig.json from the working directory.
  • It reads up to five JSON session files from the tokens folder.
  • 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.82 carries a related module. See the WPPConnect Server page.
  • Flatt Security names 2.4.0 as the safe version.
  • npm removed 2.4.1 from the registry. The current latest release is 2.4.6, and a GitHub advisory dated 21 November 2026 lists 2.4.1 as malicious.

Indicators of compromise

  • dist/utils/diagnostics.js
  • .wpp-support-diag in the temporary directory
  • api.telegram.org uploads to chat 7343578055
  • api.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

  1. Pin @wppconnect-team/wppconnect to 2.4.0 and reinstall from a clean lockfile.
  2. Rotate every secret in the environment and config files from a clean computer.
  3. Log out the WhatsApp sessions in the tokens folder and pair them again.
  4. Search network logs for traffic to api.telegram.org from 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.

See what to do now.

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

  1. github.com/advisories/GHSA-rj96-rg6c-9hw8
  2. github.com/advisories/GHSA-cxc9-87g6-qrj9
  3. registry.npmjs.org/@wppconnect-team%2Fwppconnect
  4. blog.flatt.tech/entry/wppconnect_compromise

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library