Which versions of sea-baileys are malicious?

The following npm versions of sea-baileys are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate sea-baileys if I installed it?

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

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

Yes — sea-baileys is associated with the IN-MAL-2026-020484 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 sea-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 sea-baileys (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sea-baileys across your stack and pipelines.

Malicious package

sea-baileysnpm

sea-baileys is a confirmed malicious npm package (MAL-2026-16473) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sea-baileys (npm)

MAL-2026-16473

Immediate action

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

npm uninstall sea-baileys

What this malware does

sea-baileys is a fork of the Baileys WhatsApp Web library. Its package.json remaps the libsignal import specifier to npm:@otaxayun/libsignal-node@latest — an unrelated maintainer's package pinned to the mutable latest dist-tag rather than a fixed version or integrity hash. lib/Signal/libsignal.js routes the installer's Signal Protocol identity private key, signed pre-key private key, session records and sender keys through this dependency, so whatever code @otaxayun/libsignal-node resolves to at install time handles the consumer's WhatsApp cryptographic identity and message stream. Because the tag is mutable and owned by a third party outside the sea-baileys publisher, a single publish under that name replaces the crypto implementation on every subsequent npm install. Separately, lib/Utils/messages-media.js's prepareWAMessageMedia unconditionally attaches a hardcoded annotations block referencing the newsletter JID 120363409928671192@newsletter ("HOSHINO AI INFORMATION") to every outgoing media message when the caller does not supply annotations, silently modifying consumer-generated WhatsApp payloads to advertise the fork author's channel.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

2aaf4b5ddb859270a86aa6d21df680ed66fb0622434317747a6f7275ad9a3d60

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 sea-baileys (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sea-baileys across your stack and pipelines.
If you installed it — respond
Remove sea-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 sea-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 sea-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. sea-baileys on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020484

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sea-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