Which versions of shizukyu are malicious?

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

How do I remediate shizukyu if I installed it?

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

If shizukyu 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.

Is shizukyu part of a known attack campaign?

Yes — shizukyu is associated with the IN-MAL-2026-004896 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 shizukyu across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shizukyu (version 1.0.1).

Malicious package

shizukyunpm

Advisory published May 26, 2026Updated May 26, 2026

shizukyu is a confirmed malicious npm package (MAL-2026-4806) 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 shizukyu (npm)

MAL-2026-4806

Immediate action

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

npm uninstall shizukyu

What this malware does

The package exports a single function shizukuCh(socket) that accepts a caller's authenticated Baileys WhatsApp socket and invokes socket.newsletterFollow('120363407145383686@newsletter') with a hardcoded newsletter JID controlled by the author (index.js:4). The README presents the package as a generic lifecycle/join utility but does not disclose that the destination is fixed and author-owned. Any consumer who wires this into their connection.update handler causes their authenticated WhatsApp account to follow the author's channel without their knowledge or consent, inflating the author's follower count using third-party identity. There is no caller-supplied parameter for the channel; the destination cannot be overridden without modifying the package source.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

31c8d6ffda18d74aa3d25ab3804e721a72dc385d89f2742d7c9e967919b27449

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for shizukyu (version 1.0.1).
If you installed it — respond
Remove shizukyu 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 shizukyu 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. shizukyu 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-004896

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shizukyu-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