@shadowmd/libsignal-node
Open Whisper Systems' libsignal for Node.js
This report shows the evidence for @shadowmd/libsignal-node@2.3.7, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete, unconsented runtime tampering with a foreign installed package that causes a messaging-account action. It is unrelated to the advertised libsignal functionality and is malicious.
Decision evidence
public snapshot- Importing the package automatically invokes code that patches another installed package.
- The patch locates @whiskeysockets/baileys and overwrites its newsletter source file.
- The injected replacement silently follows a fixed newsletter after the affected application starts.
- The patch creates a cache marker and later terminates the host process.
- package.json contains no npm lifecycle hook.
- No credential harvesting, environment-variable collection, or arbitrary external endpoint is present in the inspected source.
Source & flagged code
4 flagged · loading sourceManifest-reachable source overwrites another installed package with package-defined remote behavior.
install.jsView on unpkgThe patch locates @whiskeysockets/baileys and overwrites its newsletter source file.
install.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @shadowmd/libsignal-node@2.3.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing @shadowmd/libsignal-node@2.3.7. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.