MAL-2026-18440: Malicious code in @axo_cuy/baileys (npm)

Published Nov 2, 2026

Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (0b32f937714cfd8023a0123f7e15dbeb6a2146fd7f3a22f9cb5ff6728b9d3f48) 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.

Affected Software

1 affected component

npm/@axo_cuy/baileys=1.0.0

Event History

Nov 2, 2026

Advisory Published

via OSV·01:45 AM

Data Sourced

via OSV·01:45 AM

DescriptionAffected Software

Frequently Asked Questions

Who is exposed to this risk?

Systems that run npm install for @axo_cuy/baileys are exposed, because installation resolves and installs libsignal directly from the tenka-san/libsignal-node GitHub repository. This can affect developer workstations and build or deployment environments that install the package.

What does an attacker need to exploit this?

The owner or anyone who gains control of the tenka-san/libsignal-node repository could change its current HEAD. A later npm install of @axo_cuy/baileys could then retrieve the changed code and run lifecycle scripts supplied by that dependency.

Is a default installation affected?

Yes. The package declares libsignal as a hard dependency from a GitHub source without a version or commit pin, so npm install resolves the repository's current HEAD rather than a fixed reviewed artifact.

What can be done if the package cannot be removed immediately?

Avoid fresh or repeated installs that resolve the unpinned GitHub dependency. Use a controlled, reviewed copy of the dependency pinned to a specific commit and prevent installation lifecycle scripts where operationally feasible.

How can I determine whether an environment is affected?

Check whether @axo_cuy/baileys is installed or declared in project dependencies, and inspect its resolved dependency tree or lockfile for libsignal sourced from github:tenka-san/libsignal-node. Environments that have run npm install with this dependency path should be treated as potentially affected.

MAL-2026-18440: Malicious code in @axo_cuy/baileys (npm)

Affected Software

Event History

Frequently Asked Questions

Who is exposed to this risk?

What does an attacker need to exploit this?

Is a default installation affected?

What can be done if the package cannot be removed immediately?

How can I determine whether an environment is affected?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this risk?

What does an attacker need to exploit this?

Is a default installation affected?

What can be done if the package cannot be removed immediately?

How can I determine whether an environment is affected?