NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

elaina-baileysnpm

Advisory published Updated

elaina-baileys is a confirmed malicious npm package (MAL-2026-19957) that executes malicious code on install (malicious versions 0.0.0-stage, 1.0.0, 1.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in elaina-baileys (npm)

MAL-2026-19957
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall elaina-baileys

What this malware does

package.json declares the core runtime dependency libsignal as an npm alias to a third-party scoped package pinned to the mutable latest tag: "libsignal": "npm:@otaxayun/libsignal-node@latest". The upstream Baileys library uses the standard libsignal-node implementation; this fork redirects resolution to the @otaxayun scope with no version pin and no integrity hash. Every npm install of elaina-baileys resolves that alias and installs whatever bytes @otaxayun/libsignal-node currently publishes, running any lifecycle scripts shipped in that tarball on the installer's machine. Control of the delivered code sits entirely with whoever owns the @otaxayun scope and can be changed at any time without any update to elaina-baileys itself.

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

5 flagged
0.0.0-stage1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

24c66d36220f23944cbbaf0e0121785afc3c7efbb9314c0c6e7bf99e33377089
366ab3f7b886b50e134b5b59463d36e3109761400089c51865825dbe7e347606

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for elaina-baileys (5 malicious versions).

  2. If you installed it — respond

    Remove elaina-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.

  3. Did it already run?

    If elaina-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. elaina-baileys on npm has been identified as a malicious package (versions 0.0.0-stage, 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7727-99j6-9x2vIN-MAL-2026-022795

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks elaina-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.

Explore

elaina-baileys (npm) malicious package — MAL-2026-19957 | O3 Security