MAL-2026-20286: Malicious code in @ikyzanx/baileys (npm)

Published Nov 20, 2026
·
Updated

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

Source: amazon-inspector (6c64694820be3e6d15789cddda220597ead0ab1beed316980af701b4f2d0c80e) package.json declares the libsignal dependency as github:tenka-san/libsignal-node — a bare owner/repo reference with no commit SHA, tag, or version pin. On npm install, npm fetches whatever bytes are currently at the HEAD of that third-party repository and installs them, executing any lifecycle scripts contained in them, with no integrity verification. The referenced GitHub owner tenka-san is unrelated to the npm publisher of this package (@ikyzanx), so the trust boundary of installing this package silently extends to a third-party account that can push new commits to that repository at any time. The package is a Baileys fork (a WhatsApp Web client library); the unrelated-owner libsignal source is a mutable off-registry code path that executes on every install.

Affected Software

1 affected component
npm/@ikyzanx/baileys=8.5.6

Event History

Nov 20, 2026
Advisory Published
via OSV·03:51 AM
Data Sourced
via OSV·03:51 AM
DescriptionAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Any environment that runs npm install for @ikyzanx/baileys is exposed, including developer workstations and build or CI systems. Installation fetches libsignal directly from the mutable tenka-san/libsignal-node GitHub repository.

2

What does an attacker need to exploit it?

An attacker would need the ability to push commits to the tenka-san/libsignal-node repository. A subsequent npm install could then retrieve the changed repository contents and execute lifecycle scripts included in that dependency.

3

Is a default installation affected?

Yes. The declared dependency is an unpinned GitHub owner/repository reference, so npm resolves it from the repository HEAD during installation without a commit SHA, tag, version pin, or integrity verification.

4

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

Avoid fresh or uncontrolled npm installs of the package until the dependency can be pinned to a trusted immutable revision or otherwise replaced. Treat systems that install it as having a third-party GitHub trust dependency and restrict credentials and other sensitive access in those environments.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203