International
The Morning Dev

Only the news worth knowing

‹
 
B47/100

Supply-chain attack · high

WPPConnect npm releases compromised to steal secrets and WhatsApp sessions

Tier B · Patch this week – Put it in the sprint

Who’s exposed: Developers who installed WPPConnect npm versions 2.4.1 or 2.10.82

Tier B because: Exploited in the wild OR public exploit

Reach

Attack

Damage

Fix

Exploited in the wild · Secrets exposed · Supply chain

What to do

  1. Check whether WPPConnect 2.4.1 or 2.10.82 is installed in your projects or build environments.
  2. Rotate any secrets that were available to affected installs.
  3. Revoke and re-link WhatsApp sessions that may have been exposed.

The Brief

  • Malicious WPPConnect npm releases 2.4.1 and 2.10.82 were published.
  • The malicious code steals secrets and WhatsApp sessions and exfiltrates them via Telegram.
  • The releases were shipped through the project's own publishing pipeline.

Why it matters

Anyone who installed the affected WPPConnect versions may have leaked credentials and WhatsApp sessions, which can allow account takeover and access to connected systems.

The checklist behind the tier

Checklist · 4 of 10 yes
YesHits tech teamsWPPConnect is a Node.js library developers build WhatsApp integrations with.
NoCore infrastructureA single WhatsApp messaging library is not software nearly every team runs.
NoPopular toolWPPConnect is a niche WhatsApp API library, not a widely used mainstream tool.
YesExploited in the wildStep Security Blog (2026-11-17): malicious WPPConnect npm releases 2.4.1 and 2.10.82 were published and stole secrets.
NoPublic exploitStep Security Blog describes the malicious releases but does not say exploit code or a PoC is published.
NoRemote, no loginStep Security Blog does not state the attack path needs no credentials or interaction.
NoFull takeoverStep Security Blog does not explicitly state code execution, root or account takeover.
YesSecrets exposedStep Security Blog: malicious releases steal secrets and WhatsApp sessions via Telegram.
YesSupply chainStep Security Blog: malicious releases shipped through the project's own pipeline to npm.
NoNo fix yetStep Security Blog advises what to rotate; it does not say a patched version is unavailable.

Timeline

  1. Step Security Blog

    WPPConnect Compromised: Malicious Releases Steal Secrets and WhatsApp Sessions Through the Project's Own Pipeline

  2. Step Security publishes analysis of malicious WPPConnect releases

Source

WPPConnect Compromised: Malicious Releases Steal Secrets and WhatsApp Sessions Through the Project's Own Pipeline ↗ Step Security Blog · 1d ago

First seen · 1 source · Full story page · How tiers are decided