@wppconnect/server 2.10.82 exports secrets and WhatsApp session files through a hidden Telegram destination.
A new diagnostics module runs when the packaged server starts. Installing the package alone does not establish that this code ran.
What happened
The server entry point loads the added diagnostics module.
- It collects environment variables, project configuration and WhatsApp session files.
- It sends the collected text through Telegram after a 30 to 240 second delay.
- It skips recognized test and CI environments and limits reports with a temporary marker.
Vigilance caught version 2.10.82 at 03:10 UTC on 16 November 2026, 42 seconds after it went up on npm. The time to catch was 42 seconds. The Aikido malware list names this attack and shows no date. Vigilance does not count this catch as first.
Affected versions
@wppconnect/server 2.10.82contains the verified module.- The inspected
2.10.81server lacks this module. Its dependencies still need separate checks.
Indicators of compromise
dist/util/diagnostics.js.wpp-diagin the temporary directory- Telegram document uploads to chat
7343578055
How to check
Check the installed server version without starting it.
npm ls @wppconnect/server
A missing marker does not prove the module never ran.
What to do now
- Stop affected server instances and preserve their lockfiles and logs.
- Replace the affected release with reviewed code and check resolved dependencies.
- Rotate exposed configuration secrets from a clean system.
- Revoke affected WhatsApp sessions and reconnect with reviewed software.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `@wppconnect/server` 2.10.82. This version is too new or changed in a way Vigilance must check first.
In the owner report
Bad update
@wppconnect/server 2.10.82
This update now downloads from the internet, reads saved passwords and access keys and profiles this machine and its user. The version before it did not.
Frequently asked questions
Did the installer itself upload the data?
The inspected server starts the module through its runtime entry point. This finding does not establish an install-time upload.