Which versions of vinzz-wcli are malicious?

The following npm versions of vinzz-wcli are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate vinzz-wcli if I installed it?

Remove vinzz-wcli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vinzz-wcli — how do I know if it already compromised me?

If vinzz-wcli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is vinzz-wcli part of a known attack campaign?

Yes — vinzz-wcli is associated with the IN-MAL-2026-019724 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vinzz-wcli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vinzz-wcli (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vinzz-wcli across your stack and pipelines.

Malicious package

vinzz-wclinpm

vinzz-wcli is a confirmed malicious npm package (MAL-2026-16058) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vinzz-wcli (npm)

MAL-2026-16058

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall vinzz-wcli

What this malware does

vinzz-wcli is a WhatsApp CLI whose main entry (index.js) sets global.ownerr = "[email protected]" and treats any incoming WhatsApp message from that JID as coming from an authorized owner. The messages.upsert handler routes messages from owners into handleCommand, which dispatches to plugins including cmd (which calls child_process.exec on the message text) and eval (which builds and runs an AsyncFunction from the message text). When an installer runs the CLI and pairs their own WhatsApp account, the hardcoded third-party number is silently added as an owner and can send arbitrary shell commands and JavaScript to be executed on the installer's host with the installer's privileges. The tarball also ships a second file, index2.js, which is not the declared main but contains the same hardcoded owner JID and the same messages.upsert -> handleCommand dispatch, providing an equivalent execution path if that file is invoked directly.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

8dec0212466f7170f1e00ecbfe3f846cbf5d211917c3831a6ee162ca6d44ec10

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vinzz-wcli (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vinzz-wcli across your stack and pipelines.
If you installed it — respond
Remove vinzz-wcli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vinzz-wcli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vinzz-wcli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. vinzz-wcli on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019724

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vinzz-wcli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database