Which versions of kurobails are malicious?

Every published version of kurobails on npm is considered malicious. Remove the package entirely.

How do I remediate kurobails if I installed it?

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

If kurobails 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 kurobails across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kurobails (all published versions).

Malicious package

kurobailsnpm

Advisory published Oct 16, 2026Updated Nov 5, 2026

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

Malicious code in kurobails (npm)

MAL-2026-18710

Immediate action

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

npm uninstall kurobails

What this malware does

kurobails is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own authenticated WhatsApp account to an author-chosen WhatsApp Channel. Part of the campaign OX Security documented as "PhantomSub" (2026-09-28): https://www.ox.security/blog/phantomsub-malicious-npm-campaign-secretly-adds-users-to-whatsapp-spam-channels/ . Static read of the published 2.0.3 tarball on 2026-10-16 (not executed) found four channel JIDs (120363409616710069, 120363424058761303, 120363424944937940, 120363429340573125, @newsletter) decoded at runtime from base64 or char-code arrays, together with the newsletter FOLLOW query wired to run automatically after the socket connects, with errors suppressed. Same family as the withdrawn MAL-2026-4519 (chromestaff-baileys 1.1.3). Live on npm with no OSV record as of 2026-10-16. (Corrected 2026-10-16: an earlier version of this entry cited 120363421563597486, which in this package only labels forwarded messages.)

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kurobails (all published versions).
If you installed it — respond
Remove kurobails 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 kurobails 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. kurobails on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

OX Security · finder
Patrick Duggan, DugganUSA · reporter

Detect & block this

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