Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@itsmee_aizat.id/baileys2npm

Advisory published Updated

@itsmee_aizat.id/baileys2 is a confirmed malicious npm package (MAL-2026-17670) that executes malicious code on install (malicious versions 2.0.0, 2.0.1, 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @itsmee_aizat.id/baileys2 (npm)

MAL-2026-17670
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @itsmee_aizat.id/baileys2

What this malware does

package.json declares "libsignal": "github:tenka-san/libsignal-node" as a runtime dependency. The source is a GitHub user account unrelated to the package publisher (itsmeeaizat1) and unrelated to the upstream Baileys project (WhiskeySockets), with no commit SHA, tag, or integrity check. npm install resolves the current HEAD of that repository and executes any lifecycle scripts it ships, so whoever controls tenka-san/libsignal-node controls code installed on the installer's machine. The shipped lib/Signal/libsignal.js requires this dependency by name, so the pulled code is loaded at runtime as well. The separate fetchLatestBaileysVersion / fetchLatestWaWebVersion GET requests to raw.githubusercontent.com/WhiskeySockets/Baileys and web.whatsapp.com/sw.js are read-only version probes with no installer data in the request body.

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

3 flagged
2.0.02.0.12.0.2

Indicators of compromise (SHA-256)

f0b8c7ac561d44527d67a7e788e4931e2bd0676ba7439974d4b3ab0f01fa77d3
5d0bcc2a2c4a727390db5b16db5dcf2258115fbcd21410b47e7ee9dbccc7fe51
6d3966a1921328ed381d9f906a6b6ae383dd68e26af24149f494b3295e836e84
c95f98902ced2f03261621ba4cb5386a892bf31ac4510b916708d3d3eb21aa50

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @itsmee_aizat.id/baileys2 (3 malicious versions).

  2. If you installed it — respond

    Remove @itsmee_aizat.id/baileys2 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.

  3. Did it already run?

    If @itsmee_aizat.id/baileys2 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. @itsmee_aizat.id/baileys2 on npm has been identified as a malicious package (versions 2.0.0, 2.0.1, 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g6w5-p954-xcfrIN-MAL-2026-021342IN-MAL-2026-021341IN-MAL-2026-021343

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @itsmee_aizat.id/baileys2-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
@itsmee_aizat.id/baileys2 (npm) malicious package — MAL-2026-17670 | O3 Security