Which versions of wailib are malicious?

The following npm versions of wailib are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wailib if I installed it?

wailib is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed wailib — how do I know if it already compromised me?

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

Search your lockfiles and build artifacts for wailib (version 1.0.0).

Malicious package

wailibnpm

Advisory published Oct 1, 2026Updated Oct 2, 2026

wailib is a confirmed malicious npm package (MAL-2026-17451) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wailib (npm)

MAL-2026-17451

Immediate action

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

npm uninstall wailib

What this malware does

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp w:mex FOLLOW query (query_id 7871414976211147) for each target channel JID.

package/lib/Socket/messages-recv.js lines 45-72 define a char-code decoder (qvnr) and use it to build two channel JIDs, 120363428355171197@newsletter and 120363425751417260@newsletter, and the method names newsletterFollow (pzha, cited line 62: const pzha = qvnr([) and newsletterMute (wjcf, line 68), so neither the JIDs nor the method names appear in the source as text. Lines 1125-1140, in the connection.update handler, wait 30 seconds after the connection opens and then, for each JID, call sock[pzha](id) to follow the channel and, 3 seconds later, sock[wjcf](id) to mute it, so the victim is not notified of the channel's posts. There is no opt-out. The README (Portuguese) states "Sem auto-follow de canais — removida a rotina que seguia canais automaticamente apos conectar" ("No channel auto-follow — the routine that followed channels automatically after connecting was removed"), which the shipped code contradicts. The code is derived from noxleyss (MAL-2026-17402), whose name it still uses in package/lib/Utils/generics.js.

Line numbers refer to version 1.0.0.

Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in engine-requirements.js), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers.

SHA-256 of the published npm tarball(s): 1.0.0: e762bd70253081e1f523e929509e8bd5ff005feaaec6580f8f8b95ee84085920.

Malicious versions

1 flagged

1.0.0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for wailib (version 1.0.0).
If you installed it — respond
wailib is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wailib 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. wailib on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Rising Sun Solutions LLC · finder

Detect & block this

O3 blocks wailib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database