@trackking/core
This report shows the evidence for @trackking/core@99.9.1, the only known version.
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.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4460 confirms this npm version as malicious.
Advisory
MAL-2026-4460
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @trackking/core@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @trackking/core@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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.