MAL-2026-4460
Vulnerability from ossf_malicious_packages
-= 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.
- CWE-506 - The product contains code that appears to be malicious in nature.
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"domains": [
"7363616e.trackking-core.7nvupkdksbhg2wj08j2r0sf8wz23qtei.oastify.com",
"7363616e2d666466366432383439386262.trackking-core.7nvupkdksbhg2wj08j2r0sf8wz23qtei.oastify.com",
"2f686f6d652f7363616e.trackking-core.7nvupkdksbhg2wj08j2r0sf8wz23qtei.oastify.com",
"ltidi.storage.googleapis.com"
],
"evidence_files": [
{
"path": "package.json",
"sha256": "095e5845b8962521e289bac6aaa83aee8a38fad7166632a9e50731732e3039de",
"tlsh": "20e0c2645a6166334ec611b6482b995bf3b18e5f4809bc0d5beb041c829da7328f93ac"
},
{
"path": "index.js",
"sha256": "322ee46d71101bed25f260f2e78a419b5472e28d1ba02831ced05c73b44e5bb8",
"tlsh": "0e80040d043171c70355404dd140d441d4c04471400550110fc44ddd0004c0c01f0754"
}
],
"package_integrity": [
{
"filename": "core-99.9.1.tgz",
"hashes": {
"sha1": "9afce2f23e03adf1a407bfb32e76a977205d8879",
"sha512_sri": "sha512-5gp+Pq2OD+kBz8zkDsLuV8B6UK43dYc6FPuNuKlxnBLRwgfAOhLzSIhR4RIUNF4WkY+P+mhE40iPwJAjm97TPA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@trackking/core"
},
"versions": [
"99.9.1"
]
}
],
"credits": [
{
"contact": [
"actran@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-003418",
"import_time": "2026-05-26T05:50:36.377893516Z",
"modified_time": "2026-05-20T02:28:51Z",
"sha256": "64d51e587bc0b6508fa3d38027f18d42d9ab4b6ccdb8dd2760543e8c52d6bb18",
"source": "amazon-inspector",
"versions": [
"99.9.1"
]
},
{
"id": "IN-MAL-2026-003419",
"import_time": "2026-05-26T05:50:36.496193809Z",
"modified_time": "2026-05-20T02:28:51Z",
"sha256": "dee796b7c87d0f0fb769d15210d16bab9fe1e2783726e0b3033ee0eac944d62f",
"source": "amazon-inspector",
"versions": [
"99.9.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (64d51e587bc0b6508fa3d38027f18d42d9ab4b6ccdb8dd2760543e8c52d6bb18)\n@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 \u2014 `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.6.tgz` \u2014 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.\n",
"id": "MAL-2026-4460",
"modified": "2026-05-26T05:55:01Z",
"published": "2026-05-20T02:28:51Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@trackking/core/v/99.9.1"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @trackking/core (npm)"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.