@wanzlonely/bails4u@7.0.0
Vulnerability report · Last retrieved from osv.dev October 29, 2026 at 4:00 PM UTC
OSV ID
MAL-2026-17381
Ecosystem
npm
Summary
package.json declares libsignal as github:wanzchil/libsignal-node with no commit SHA, tag, or semver pin. On npm install, this dependency source is resolved to the current HEAD of that GitHub repository, fetched, and installed — including execution of any lifecycle scripts (preinstall/install/postinstall/prepare) present in that repo's tree at the moment of resolution. There is no integrity check and no version pinning, so the code executed on the installer's machine at install time is whatever the owner of wanzchil/libsignal-node has pushed to the default branch at that instant, and can change from install to install without any change to this package. This is an off-registry dependency source: the manifest itself is the installation vector, independent of the current contents of the referenced repository.
Source: amazon-inspector (5d496ed2775d23d1d9e2a557ca88aaedbcc6b68b89d5f0f7cd54f1092ab431cf)
Protect your entire dependency tree
Scan your lock files automatically on every PR. Block malicious packages before they reach production.