Which versions of @axo_cuy/baileys are malicious?

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

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

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

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

Yes — @axo_cuy/baileys is associated with the IN-MAL-2026-022477 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 @axo_cuy/baileys across my projects, lockfiles, and CI pipelines?

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

Malicious package

@axo_cuy/baileysnpm

Advisory published Nov 2, 2026Updated Nov 2, 2026

@axo_cuy/baileys is a confirmed malicious npm package (MAL-2026-18440) 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 @axo_cuy/baileys (npm)

MAL-2026-18440

Immediate action

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

npm uninstall @axo_cuy/baileys

What this malware does

package.json declares a hard dependency libsignal with the source github:tenka-san/libsignal-node. This is an off-registry dependency source: npm install resolves it to the current HEAD of that third-party GitHub repository with no version/commit pin and no integrity check, and executes any lifecycle scripts shipped by that repository on the installer's machine. The owner of tenka-san/libsignal-node can change the installed code at any time without republishing this package. The target repository is not the upstream Baileys/libsignal publisher, so installation introduces a third-party code path that bypasses registry review and dependency pinning.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0b32f937714cfd8023a0123f7e15dbeb6a2146fd7f3a22f9cb5ff6728b9d3f48

Detection & response playbook

Malicious package

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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