Which versions of @mikudeveloper/baileys are malicious?

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

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

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

If @mikudeveloper/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 @mikudeveloper/baileys part of a known attack campaign?

Yes — @mikudeveloper/baileys is associated with the IN-MAL-2026-020294, GHSA-2xx9-x9v7-25x2 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 @mikudeveloper/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mikudeveloper/baileys (version 1.0.0).

Malicious package

@mikudeveloper/baileysnpm

Advisory published Sep 22, 2026Updated Oct 12, 2026

@mikudeveloper/baileys is a confirmed malicious npm package (MAL-2026-16386) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mikudeveloper/baileys (npm)

MAL-2026-16386

Immediate action

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

npm uninstall @mikudeveloper/baileys

What this malware does

This package is a fork of Baileys that declares libsignal in package.json as github:tenka-san/libsignal-node — a git dependency with no commit SHA, tag, or integrity check, resolving to whatever HEAD returns at install time and executing any lifecycle scripts inside it. The referenced GitHub account is unrelated to the upstream WhiskeySockets/libsignal-node maintainer, so its owner controls install-time code on every installer of this package. Separately, makeNewsletterSocket schedules a 120-second setTimeout after connection that fetches a channel-ID list from a hardcoded, mutable URL (raw.githubusercontent.com/MikuDevReal/V2.0/refs/heads/main/pepek.json) and issues QueryIds.FOLLOW on each entry using the installer's authenticated WhatsApp session, silently subscribing them to author-selected channels with no disclosure in the README. The remote list is author-mutable, so follow targets can change at any time.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d03bf7166a5353a0b22409ebbb724ee53f24394c9ff340df668c970772796e28

ae1cbd433ff843bbf543121e434bdbc4cdfe37c00055a4709849f191c0f58fbb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mikudeveloper/baileys (version 1.0.0).
If you installed it — respond
Remove @mikudeveloper/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 @mikudeveloper/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. @mikudeveloper/baileys 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.

Campaign

IN-MAL-2026-020294GHSA-2xx9-x9v7-25x2

References

Credits

Amazon Inspector · finder

Detect & block this

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