취약점

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (64d51e587bc0b6508fa3d38027f18d42d9ab4b6ccdb8dd2760543e8c52d6bb18)

@trackking/core@99.9.1 is an empty stub: index.js is module.exports = {}, package.json has no description, no author, ISC license, and a high-number version (99.9.1) typical of dependency-confusion uploads. Its sole effect on installation is a dependencies entry pointing ltidisafe at an arbitrary HTTPS tarball hosted on a Google Cloud Storage bucket — https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.6.tgz — rather than the npm registry. The path segment literally reads depenconf (dependency-confusion). On npm install, npm fetches and installs this out-of-band tarball, executing any lifecycle scripts it contains, with no registry review, no namespace pinning, and no signature verification. The tarball cannot be inspected from this package, but the lure shape (empty stub + placeholder metadata + version-99.9.1 + arbitrary-URL dep with a depenconf path) is unambiguously an attack delivery vehicle, not a legitimate library.