Which versions of @prototypevip/baileys are malicious?

The following npm versions of @prototypevip/baileys are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate @prototypevip/baileys if I installed it?

Remove @prototypevip/baileys 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 @prototypevip/baileys — how do I know if it already compromised me?

If @prototypevip/baileys 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 @prototypevip/baileys part of a known attack campaign?

Yes — @prototypevip/baileys is associated with the IN-MAL-2026-016854 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 @prototypevip/baileys 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 @prototypevip/baileys (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @prototypevip/baileys across your stack and pipelines.

Malicious package

@prototypevip/baileysnpm

@prototypevip/baileys is a confirmed malicious npm package (MAL-2026-13480) that executes malicious code on install (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @prototypevip/baileys (npm)

MAL-2026-13480

Immediate action

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

npm uninstall @prototypevip/baileys

What this malware does

@prototypevip/baileys is a fork of the Baileys WhatsApp library. lib/Store/prototype-store.js registers a listener on the 'messages.upsert' event that runs on every incoming message. The listener body is obfuscated behind a base64 string table and a decoder (Buffer.from(s,'base64').toString('utf8')), which resolves to the property names 'type', 'md', 'ws', 'sendMessage', an Arabic message body ('you are no longer authorized to use this bot'), and the marker 'gintoki'. When the routine walks the message object and locates the active WhatsApp socket (type=='md', ws truthy), it compares an adjacent key against the decoded literal 'gintoki'. On any installer whose bot is not tagged with that hardcoded owner string, the code invokes the installer's own socket's sendMessage to broadcast the Arabic 'no longer authorized' notice through the installer's WhatsApp account and then throws 'Blocked' (also base64-decoded) to halt message handling. The behavior is undocumented, is hidden by base64 obfuscation of every relevant string, and abuses the installer's authenticated WhatsApp session as the delivery channel to send attacker-authored content to the installer's own contacts.

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

f4b0068015e90b8e47dd9b67c66ed1d0b0cc4c1ebccd985f08efd31837d27ce8

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 @prototypevip/baileys (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @prototypevip/baileys across your stack and pipelines.
If you installed it — respond
Remove @prototypevip/baileys 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 @prototypevip/baileys 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 @prototypevip/baileys 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. @prototypevip/baileys on npm has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016854

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @prototypevip/baileys-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