unleash-js

unleash-js@99.9.1 is an empty stub package (index.js exports `{}`, 35 bytes; no author, no description) whose sole effect is to pull a chained dependency `ltidisafe` from an arbitrary tarball URL on a third-party Google Cloud Storage bucket: `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.7.7.tgz`. The host is not the package publisher's domain, the tarball is unpinned by hash, and the bucket is mutable — any installer running `npm install unleash-js` will fetch and execute whatever bytes currently sit at that URL, including any lifecycle scripts (preinstall/install/postinstall) inside the fetched tarball. The 99.9.1 version, empty metadata, and `depenconf` path segment are consistent with a dependency-confusion squat targeting an internal package name; the stub's only purpose is to act as a loader for the externally hosted payload. ## Source: ghsa-malware (80b8d9c68487241999f1fab34c717c7a4405f1a5ecefb4a22e2e7fa8cdbdbba1) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (d00549f2feef5f3af06b3625effca261dd2be514ae05dc1b21c60e3cb9d1b23b) The OpenSSF Package Analysis project identified 'unleash-js' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.