@library-wide/library-shell
This report shows the evidence for @library-wide/library-shell@99.9.1. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe remote dependency’s automatic preinstall sends identifying host and user data to an unrelated fixed collector without an installer consent guard. This is concrete installation-time data exfiltration.
Decision evidence
public snapshot- The package declares a dependency on the remote ltidisafe tarball.
- That dependency’s preinstall runs test.js automatically.
- test.js places the hex-encoded username, hostname, and home directory in hostnames under a fixed OAST domain and invokes requests for them.
- The dependency implementation sends HTTP GET requests to the supplied URL.
Source & flagged code
6 flagged · loading sourceThe package declares a dependency on the remote ltidisafe tarball.
package.jsonView on unpkg · L9Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @library-wide/library-shell@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @library-wide/library-shell@99.9.1. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.