OpenSSF/OSV advisory MAL-2026-4460 confirms this npm version as malicious. @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 —...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @trackking/core (npm)
Details
@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.
Decision reason
OpenSSF Malicious Packages via OSV confirms @trackking/core@99.9.1 as malicious (MAL-2026-4460): Malicious code in @trackking/core (npm)