@kasabaileys/baileys@0.0.0-stage
Malicious code in @kasabaileys/baileys (npm)
Analysis
@kasabaileys/baileys@0.0.0-stage is a name-reservation placeholder published under an unofficial scope that impersonates the widely used @whiskeysockets/baileys WhatsApp Web API client library — it uses the same "baileys" basename but is not published under the upstream scope and makes no claim to that project. The version contains no executable code at all: only package.json and README.md (342 bytes total, no lifecycle scripts, no bin entries, no dependencies). Its package.json sets "stub": true with the description "Temporary package placeholder for staged publishing", and the README states it is a "temporary placeholder" for which "an operational version to replace this has been submitted for review and is awaiting a staged release". In other words the publish reserves and holds the impersonating package name while a later, code-bearing version is staged for release. No network endpoints, hosts, IPs, dropped files or credential access exist in this version — the artifacts are the impersonating scope/name @kasabaileys/baileys and version 0.0.0-stage, which should be treated as staging infrastructure for a supply-chain impersonation rather than a usable package.
- analyzed by
- Leitwacht
- first seen
- Nov 16, 2026, 06:32 PM
- analyzed
- Nov 16, 2026, 06:33 PM
Related advisories
- @kasabaileys/baileys@2.0.2 same package
- @shadowmd/libsignal-node@0.0.0-stage
- events-runtime@0.0.0-stage
- minidate-fmt@0.0.0-stage
- @axo_cuy/baileys@5.0.0
- @sakataa/baileys@5.0.1
- amlekzo@1.1.0
- baileys-clean@7.3.2
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.