MalwarePublished 2 Nov 2026

@bil-rgb/baileys (npm) · Malicious Code

Affects @bil-rgb/baileysSource GCVE Database

Malicious package : remove @bil-rgb/baileys and rotate any secrets on hosts that installed it.

Data as of 2 Nov 2026, 04:44 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18441

What to do

Remove @bil-rgb/baileys from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@bil-rgb/baileys	Affected =1.0.0 =1.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The @bil-rgb/baileys npm package versions 1.0.0 and 1.0.1 declare a dependency on a libsignal library hosted in a personal GitHub repository without specifying a commit SHA, tag, or integrity check. This allows the dependency to resolve to the latest code at the repository's HEAD during installation, enabling arbitrary code execution controlled by the repository owner at install time. The package itself is a fork of Baileys, but the critical risk arises from the uncontrolled external dependency resolution.

Impact

Users installing @bil-rgb/baileys versions 1.0.0 or 1.0.1 risk executing arbitrary code controlled by the owner of the external GitHub repository referenced in the dependency. This can lead to compromise of the install environment, including potential data theft, system compromise, or further malware deployment. The impact is limited to those who install these specific package versions with the vulnerable dependency declaration.

Defensive guidance

Avoid installing @bil-rgb/baileys versions 1.0.0 and 1.0.1. If already installed, remove these versions and do not trust the package due to its uncontrolled external dependency. Monitor for any vendor advisories or updates regarding this package. Since this is a supply chain risk via npm dependency resolution, strict verification of dependencies and use of lockfiles or integrity checks is recommended.

Summary

The @bil-rgb/baileys package versions 1.0.0 and 1.0.1 specify their libsignal dependency as github:tenka-san/libsignal-node without pinning to a specific commit or including integrity verification. When npm installs this package, it clones the current HEAD of the personal GitHub repository of user tenka-san and executes any lifecycle scripts present there. Since this repository is unrelated to the official signalapp/libsignal-node or the Baileys publisher, the code executed during installation is fully controlled by the personal GitHub user, allowing potential malicious code execution on the installer's machine. This behavior effectively makes the package a malicious supply chain vector.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Nov 2026, 04:44 UTC

Technical details

References

Community reviews