@trackking/core

Details

---
_-= 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.

## Source: ghsa-malware (cd0a05f7bcae1bff04a0761332ae20f7fb3b25e115ebf420ebf5db20d0d55a1c)
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.

Compromised versions (1)

• 99.9.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.