Which versions of @ubedsockets/baileys are malicious?

The following npm versions of @ubedsockets/baileys are flagged malicious: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.6.8, 1.6.9, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.5, and 6 more. Treat any of these as compromised.

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

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

If @ubedsockets/baileys 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 @ubedsockets/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ubedsockets/baileys (26 malicious versions).

Malicious package

@ubedsockets/baileysnpm

Advisory published Nov 2, 2026Updated Nov 4, 2026

@ubedsockets/baileys is a confirmed malicious npm package (MAL-2026-18600) that executes malicious code on install (malicious versions 1.0.0, 1.1.0, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ubedsockets/baileys (npm)

MAL-2026-18600

Immediate action

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

npm uninstall @ubedsockets/baileys

What this malware does

Malicious package. @ubedsockets/baileys is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). On connection it issues an authenticated w:mex newsletter FOLLOW mutation (query_id 7871414976211147) that silently subscribes every victim to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363410154606795@newsletter, 120363423295236859@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious. Detected by wormsign static analysis of the injected channel-subscription code.

Malicious versions

26 flagged

1.0.01.1.01.2.01.3.01.4.01.5.01.6.11.6.21.6.31.6.41.6.51.6.61.6.71.6.81.6.91.7.01.7.11.7.21.7.31.7.51.7.61.7.71.7.91.7.101.7.111.7.12

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @ubedsockets/baileys (26 malicious versions).
If you installed it — respond
Remove @ubedsockets/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 @ubedsockets/baileys 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. @ubedsockets/baileys on npm has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.1, 1.6.2, and 18 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

wormsign.io

Credits

wormsign · finder

Detect & block this

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