GHSA-rj96-rg6c-9hw8Malicious WPPConnect library release
Importing library 2.4.1 loads a module that collects host data and session tokens.
Malicious WPPConnect code shipped through its release pipeline in two npm packages, a GitHub nightly and Docker images. It collects process secrets and WhatsApp session data for a Telegram bot. The library’s npm latest tag was rolled back.
The module runs on import in the WhatsApp automation library and at startup in the server. It reads environment variables, files such as .env and config.json, and WhatsApp token files from the working directory. It looks up the host’s public IP, then attempts to send collected data to a Telegram bot. A server dependency range of ^2.3.6 for the library also allows a vulnerable install unless the resolved version is pinned.
StepSecurity found that the library’s valid npm provenance pointed to the compromised build, while the later Git tag pointed to different source. It verified the two affected Docker images and a GitHub nightly artifact. The floating image tags latest, 2 and 2.10 pointed to the 2.10.83 image until 03:54 UTC on November 16. Treat the main tag before 07:31 UTC that day as unverified. Package pipeline logs also reference library 2.4.3 and server 2.10.83, which were absent from the npm registry metadata examined. Check locally cached artifacts even after the registry rollback.
The 155 downloads that StepSecurity cited cover only part of the affected library’s time as npm latest. They cannot establish the number of installations, executions or successful uploads. The preliminary containment record also leaves control of the publishing account and revocation of the Telegram credentials unresolved.
GHSA-rj96-rg6c-9hw8Importing library 2.4.1 loads a module that collects host data and session tokens.
GHSA-96hm-h5v4-92fqStarting server 2.10.82 loads a similar module. Its library dependency provides a second execution path.
Nov 15, 22:34 UTC
Malicious commits land on the library branch
StepSecurity traced the module and its import to unsigned commits on the default branch. The release workflow then ran.
Nov 15, 23:31 UTC
npm publishes library 2.4.1
It becomes latest and carries a valid provenance attestation for the malicious build.
Nov 16, 02:48–03:09 UTC
Container images and the server package ship
Docker images tagged 2.10.82 and 2.10.83 contain the payload. npm publishes server 2.10.82 at 03:09 UTC.
Nov 16, 04:00 UTC
Researcher publicly reports both npm releases
The project’s default branches were force-pushed shortly after the issues opened. Both affected npm versions were deprecated. The library’s latest tag returned to 2.4.0. The server’s 2.10.82 was never tagged latest.
Nov 17, 2026
GitHub publishes two malware advisories
GitHub lists the affected npm versions. These remain separately identifiable from the Docker and nightly artifacts.
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.