Which versions of shin-yagami are malicious?

The following npm versions of shin-yagami are flagged malicious: 2.0.4. Treat any of these as compromised.

How do I remediate shin-yagami if I installed it?

Remove shin-yagami 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 shin-yagami — how do I know if it already compromised me?

If shin-yagami was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find shin-yagami across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shin-yagami (version 2.0.4).

Malicious package

shin-yagaminpm

Advisory published Oct 27, 2026Updated Nov 9, 2026

shin-yagami is a confirmed malicious npm package (MAL-2026-19015) that executes malicious code on install (malicious version 2.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shin-yagami (npm)

MAL-2026-19015

Immediate action

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

npm uninstall shin-yagami

What this malware does

shin-yagami is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in WhatsApp/node.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363421179449531@newsletter, using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).

Malicious versions

1 flagged

2.0.4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for shin-yagami (version 2.0.4).
If you installed it — respond
Remove shin-yagami 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 shin-yagami was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

References

Credits

CyberXYZ · finder

Detect & block this

O3 blocks shin-yagami-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