wppconnect-npm-trusted-publishing-stealer
Unattributed attacker hijacked WPPConnect's trusted publishing workflow to ship a WhatsApp session and credential stealer to npm
Posted · Spectrum Delta Research Team
Summary
An unattributed attacker using the WPPConnect maintainer account joaosouz4dev pushed unsigned commits that shipped a secret-stealing module through the project's own trusted GitHub Actions publishing workflow. On 15 and 16 November 2026 the releases @wppconnect-team/wppconnect 2.4.1/2.4.3 and @wppconnect/server 2.10.82/2.10.83, plus Docker images and a GitHub nightly build, carried a diagnostics module that copies every environment variable, reads .env and config files, and takes WhatsApp session tokens from tokens/ and wppconnect_tokens/. It uploads the data to Telegram bot 9034051102 (chat 7343578055) after a random 30 to 240 second delay, at most once per 24 hours, and stays silent on CI and sandbox hosts. The code runs on library import or server start, so npm install --ignore-scripts does not prevent it, and the 2.4.1 release carried a valid SLSA provenance attestation. Maintainers rolled the latest tag back, deprecated the bad releases and rewrote the git history within hours, but every secret reachable from an affected process should be treated as exposed. Amazon Inspector and Bitbison found the malicious code; the source of the maintainer-account access is unknown.
Breakdown
Targets
- Industry: WhatsApp business automation developers
- Industry: Technology and SaaS
Technical exposure
- Installs of @wppconnect packages 2.4.1, 2.4.3, 2.10.82 or 2.10.83
- Docker pulls of wppconnect/wppconnect-server images on 16 November
- WhatsApp session token files under tokens/ or wppconnect_tokens/
- Environment variables and .env files on hosts running the library
Adversary
Unattributed · commits under maintainer account joaosouz4dev; StepSecurity has not established how access was obtained (B/2)
Procedures (3)
Hijacked maintainer account publishes stealer via trusted workflow
Logs
GitHub audit and workflow logs · Tag pushes and release workflow runs under the joaosouz4dev account on 15-16 November 2026 publishing @wppconnect-team/wppconnect 2.4.1 and @wppconnect/server 2.10.82; unsigned direct commits to default branches, workflow run 43770170170, git history later rewritten by force push
CI/CD install logs · npm install or workflow logs resolving @wppconnect-team/wppconnect 2.4.1 or 2.4.3, @wppconnect/server 2.10.82 or 2.10.83, or Docker pulls of wppconnect/wppconnect-server images between 02:48 and 07:31 UTC on 16 November 2026
Diagnostics module collects secrets and WhatsApp session tokens
Logs
- EDR process and file events · node process reading .env, .env.local, .env.production, config.js, config.json, ormconfig.json and tokens/*.json or wppconnect_tokens/ in a WPPConnect project, creating the marker file .wpp-support-diag in the temp directory, and fetching api.ipify.org for the host public IP
Exfiltration to Telegram Bot API after random delay
Logs
- Web proxy and DNS logs · Outbound HTTPS POST to api.telegram.org bot 9034051102 (method sendDocument, chat_id 7343578055) from developer or server hosts, 30 to 240 seconds after a WPPConnect process starts; the module stays silent on hosts where CI, GITHUB_ACTIONS or RUNNER_ variables are set
Indicators of compromise
Domains (2)
- api.telegram.orgTelegram Bot API exfiltration endpoint; bot 9034051102, chat_id 7343578055
- api.ipify.orgPublic IP lookup performed before exfiltration
URLs (1)
- https://api.telegram.org/bot9034051102/sendDocumentExfiltration POST target; multipart document upload carrying env vars, config files and WhatsApp session tokens
Hashes (2)
- 06158b832fb2aeb5482202c944bc8f23d59f5cf35c0dc66e926c2e395e5673a0dist/utils/diagnostics.js in @wppconnect-team/wppconnect 2.4.1
- a8fd315c910cf0d0e84e7a642c0fd70b8e4ca20673ba0cba1f8b69392c944f2ddist/util/diagnostics.js in @wppconnect/server 2.10.82
Sources
- B/2StepSecurity blog
- B/1OpenSSF malicious-packages records
- B/1WPPConnect GitHub issue 2734
- C/2Corgea research
Grades are source reliability (A–F) and information credibility (1–6).
Questions, detections or sightings of wppconnect-npm-trusted-publishing-stealer? Bring them to the community.