@shadowmd/libsignal-node@0.0.0-stage
Malicious code in @shadowmd/libsignal-node (npm)
Analysis
This publish of @shadowmd/libsignal-node (version 0.0.0-stage) contains no executable code: the tarball is ~350 bytes with only package.json and README.md, no scripts, no bin entries, no dependencies and no install hooks. The package.json sets "stub": true and describes itself as a "Temporary package placeholder for staged publishing", and the README states that an "operational version ... is awaiting a staged release". The package re-uses the unscoped name libsignal-node — the canonical package name of the Signal messaging protocol JavaScript binding — under an unrelated @shadowmd scope. Analysis of this version is metadata-only: there is no code to inspect, no network destination, and no credential access in these bytes. Prior versions published under this package name have been identified as malicious; this release is a name-holding placeholder and should be treated as staging for a follow-up version that would carry the actual payload.
- analyzed by
- Leitwacht
- first seen
- Nov 16, 2026, 06:32 PM
- analyzed
- Nov 16, 2026, 06:33 PM
Related advisories
- 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
- @wppconnect/server@2.10.82
- wizeza-baileys@2.0.7
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.