MAL-2026-18441: Malicious code in @bil-rgb/baileys (npm)

Published Nov 2, 2026

Updated

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

Source: amazon-inspector (3bcbf6493a6aa37ccc827723d6fd73b082c66d10a549af2413aba2a8a6f47b7f) package.json for @bil-rgb/baileys@1.0.0 declares its libsignal dependency as github:tenka-san/libsignal-node with no commit SHA, no tag, and no integrity check. npm install resolves this value by cloning whatever currently exists at HEAD of that personal GitHub user's repository and running any lifecycle scripts contained in it. The resolution target is a personal user account unrelated to the upstream signalapp/libsignal-node or WhiskeySockets Baileys publisher, so the code that executes on an installer's machine at install time is whatever that account chooses to place in the referenced branch at the moment of install, independent of this package's own tarball contents. The remainder of the package body (lib/Utils/generics.js and surrounding files) is a Baileys fork; the install-time attacker control is produced by the manifest line itself.

Affected Software

1 affected component

npm/@bil-rgb/baileys=1.0.0, =1.0.1

Event History

Nov 2, 2026

Advisory Published

via OSV·01:41 AM

Data Sourced

via OSV·01:41 AM

DescriptionAffected Software

Frequently Asked Questions

What action triggers the attacker-controlled code path?

Installing the package triggers npm to resolve the libsignal dependency by cloning the current HEAD of github:tenka-san/libsignal-node. Any lifecycle scripts in that repository can run on the installer's machine during installation.

Why is the dependency reference unsafe even if the published package tarball is unchanged?

The dependency is not pinned to a commit SHA or tag and has no integrity check. Its contents can change whenever the referenced GitHub account updates the repository, independently of @bil-rgb/baileys itself.

Which installations are exposed?

Installations of @bil-rgb/baileys that resolve its declared libsignal dependency from the referenced GitHub repository are exposed to whatever is at that repository's HEAD at install time. The affected manifest declaration is documented for @bil-rgb/baileys@1.0.0.

MAL-2026-18441: Malicious code in @bil-rgb/baileys (npm)

Affected Software

Event History

Frequently Asked Questions

What action triggers the attacker-controlled code path?

Why is the dependency reference unsafe even if the published package tarball is unchanged?

Which installations are exposed?

Company

Resources

Contact

Frequently Asked Questions

What action triggers the attacker-controlled code path?

Why is the dependency reference unsafe even if the published package tarball is unchanged?

Which installations are exposed?