Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

WPPConnect Malicious npm and Docker Releases: What to Check

WPPConnect malicious releases reached npm, nightly builds and Docker images. Check versions and digests, rotate reachable secrets, and re-pair WhatsApp.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
17 November 2026
Reading time
4 min read
Abstract package release channels illustrating a software supply chain investigation.

WPPConnect malicious releases reached npm, a GitHub nightly asset, and Docker images on 15 and 16 November 2026, according to StepSecurity. Identify installed versions and image digests now. StepSecurity names library 2.4.0 and server 2.10.81 as clean versions to pin while investigating exposure.

The issue concerns code delivered through the project’s own release pipeline. For teams using third party risk management software, affected packages and images are supplier dependencies to track. StepSecurity says the code copied environment variables, configuration secrets, and WhatsApp session tokens to a Telegram bot when the library loaded or the server started. Installation alone does not establish that the code ran.

WPPConnect Malicious Releases: Which Builds Need Review?

StepSecurity identifies npm library 2.4.1 and server 2.10.82 as malicious releases. Its workflow review also found payload-bearing 2.4.3 and 2.10.83 builds, although those versions were not listed by npm at the time. Search lockfiles and deployed artifacts for all four versions, including transitive library installs through the server.

Channel Review Safer pin or verification
npm library 2.4.1; check 2.4.3 and 2.4.2 as precautions Pin 2.4.0
npm server 2.10.82; check 2.10.83 Pin 2.10.81 and override its library dependency to 2.4.0
Docker and nightly 2.10.82, 2.10.83, floating tags, and nightly assets from the incident window Compare image digests and build provenance with a reviewed artifact

StepSecurity says Docker floating tags pointed to a malicious image until 03:54 UTC on 16 November. A nightly asset was replaced at 03:53 UTC; current tags and download pages cannot identify previously deployed artifacts. The researchers did not verify replacement images as clean, so inspect the deployed digest and its origin.

npm recorded 155 downloads of library 2.4.1 in a reporting window covering only about 28 minutes of its availability, StepSecurity says. That figure is a partial download count, not a count of infected installations or compromised accounts. Brandefense Blackhole counted one dark-chat post mentioning WPPConnect from 19 August to 17 November 2026; the measured unit is a post, not an attack.

Why Did Trusted Publishing Miss the Problem?

StepSecurity says the code entered through unreviewed commits and then the project’s normal workflows published the artifacts. The library package carried a valid provenance attestation for the malicious build. Provenance showed where it was built, but did not establish that anyone reviewed the source.

The researchers observed force-pushes after public issue reports and say a release tag now points to different code from the published npm package. GitHub shows the account used in these actions, not the person controlling it. StepSecurity could not establish how access was obtained, so attribution and entry method remain open.

The code ran at import or startup, according to StepSecurity; skipping npm install scripts would not prevent that trigger. An malicious npm package can therefore expose a runtime even when install-time hooks are disabled. Track release evidence and response priorities while checking the exact local artifacts.

What Should Maintainers and Operators Do Now?

Inventory lockfiles, installed packages, container digests, and nightly assets across developer machines, CI, and production. Establish whether a suspect package was imported or an affected image started. Preserve relevant build, application, and outbound network logs before replacing artifacts.

WPPConnect response order
  • Find affected artifactsRecord package versions, dependency trees, nightly assets, and running image digests.
  • Assess executionCheck whether suspect code loaded on each host or CI runner.
  • Rotate reachable secretsReplace process environment and configuration credentials from a clean machine.
  • Re-pair WhatsAppUnlink affected devices, retire old session tokens, and pair again after a clean pin.
  • Verify replacementsPin reviewed packages and images, then confirm deployed versions and digests.

StepSecurity advises treating secrets reachable by a process that loaded the code as stolen. Rotate environment and configuration credentials from a clean machine, unlink WhatsApp devices, remove old session tokens, and pair again only after pinning reviewed artifacts. A software supply chain compromise can cross package and container channels, so verify each channel independently.

Pin library 2.4.0 and server 2.10.81 with a committed lockfile, including an override for the server’s library dependency, as StepSecurity recommends. Do not assume a floating Docker tag or rewritten source tag proves an earlier deployment was safe. StepSecurity said publishing-account containment was unconfirmed; review newer releases before adoption.

Frequently Asked Questions

Which WPPConnect versions should teams investigate?

Check library 2.4.1 and 2.4.3, server 2.10.82 and 2.10.83, and Docker or nightly artifacts from the incident window. StepSecurity also recommends checking library 2.4.2 as a precaution.

Does 155 downloads mean 155 compromised installations?

No. StepSecurity says the npm count covers only part of the release window. Downloads do not show whether the code loaded or how many systems were affected.

What if a suspect WPPConnect build ran?

StepSecurity advises rotating reachable environment and configuration secrets from a clean machine. Unlink WhatsApp devices, retire old session tokens, and pair again after pinning reviewed artifacts.

Sources

  1. StepSecurity: WPPConnect Compromised, 16 November 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →