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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

Yes — @mikudeveloper/baileys is associated with the IN-MAL-2026-020294 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mikudeveloper/baileys (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mikudeveloper/baileys across your stack and pipelines.

Malicious package

@mikudeveloper/baileysnpm

@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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d03bf7166a5353a0b22409ebbb724ee53f24394c9ff340df668c970772796e28

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mikudeveloper/baileys (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mikudeveloper/baileys across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @mikudeveloper/baileys before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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-020294

References

npmjs.com

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