Which versions of @sahril2nd/baileys are malicious?

The following npm versions of @sahril2nd/baileys are flagged malicious: 1.0.21. Treat any of these as compromised.

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

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

If @sahril2nd/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.

Is @sahril2nd/baileys part of a known attack campaign?

Yes — @sahril2nd/baileys is associated with the IN-MAL-2026-019902 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 @sahril2nd/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sahril2nd/baileys (version 1.0.21).

Malicious package

@sahril2nd/baileysnpm

Advisory published Sep 9, 2026Updated Sep 9, 2026

@sahril2nd/baileys is a confirmed malicious npm package (MAL-2026-16105) that steals credentials and exfiltrates sensitive data (malicious version 1.0.21). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sahril2nd/baileys (npm)

MAL-2026-16105

Immediate action

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

npm uninstall @sahril2nd/baileys

What this malware does

This package is a fork of the Baileys WhatsApp library that embeds a hardcoded network destination hidden as a String.fromCharCode(...) decimal-ASCII array inside lib/Socket/messages-send.js. The decoded bytes at lines 425 and 436 reconstruct the URL https://fiora.nixel.my.id/ — a host unrelated to any documented Baileys/WhatsApp infrastructure. The destination is assembled at call-time from a numeric array rather than appearing as a plain-text literal, which is a deliberate concealment technique on the message-send code path where WhatsApp session data and outbound message content are handled. Obfuscated construction of a non-first-party destination inside the messaging pipeline of a WhatsApp client library is the shape of session/message exfiltration to an author-controlled endpoint.

Malicious versions

1 flagged

1.0.21

Indicators of compromise (SHA-256)

a3d2089d9678322dc8adbf5e6e740c29d6720133df3489970652a2100641435e

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-019902

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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