mal-2026-17631
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (078ce187b38122a7eff5def33454871232cdd38bde7d35e7ee1968d0e98cd45c)
package.json declares its sole dependency ltidisafe as a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.3.tgz) hosted on a third-party Google Cloud Storage bucket rather than a registry version range. On npm install, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts inside the fetched tarball on the installer's host with no version pin, no hash, and no integrity check — whoever controls that bucket controls code executed at install time. The shipped index.js is an empty stub (module.exports = {}), so the package's only effect is to pull in the off-registry archive. The package is published under the @pinecone-experience scope at version 99.9.1 — an implausibly high version under a vendor-looking scope, matching the dependency-confusion shape where a high version is used to win resolution against an internal package of the same name.
- 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": {
"evidence_files": [
{
"path": "package.json",
"sha256": "3d0f82bc0b4bfb84b1de4e0ed99ebe09770d2fd88a73c004ed0c073bc491d803",
"tlsh": "afe07d200a6459330ec611b34c1a6007f3705e4f040dbc0c1fdf041c418ca7328fa35c"
}
],
"package_integrity": [
{
"filename": "messages-99.9.1.tgz",
"hashes": {
"sha1": "4f8b56ad8cc638fef12f675b2c7e8b9bdc2a1d8b",
"sha512_sri": "sha512-axbG6UiFQ9shz9HSUlsA6CXEUilYJHh/83SN/QSjN646tEf/I2jTGF+1za89i6vtLa+wUKOQ4gamuRnYi+7AJA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@pinecone-experience/messages"
},
"versions": [
"99.9.1"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021089",
"import_time": "2026-10-06T04:22:56.270091881Z",
"modified_time": "2026-10-06T03:57:14Z",
"sha256": "078ce187b38122a7eff5def33454871232cdd38bde7d35e7ee1968d0e98cd45c",
"source": "amazon-inspector",
"versions": [
"99.9.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (078ce187b38122a7eff5def33454871232cdd38bde7d35e7ee1968d0e98cd45c)\npackage.json declares its sole dependency `ltidisafe` as a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.3.tgz) hosted on a third-party Google Cloud Storage bucket rather than a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts inside the fetched tarball on the installer\u0027s host with no version pin, no hash, and no integrity check \u2014 whoever controls that bucket controls code executed at install time. The shipped index.js is an empty stub (`module.exports = {}`), so the package\u0027s only effect is to pull in the off-registry archive. The package is published under the `@pinecone-experience` scope at version 99.9.1 \u2014 an implausibly high version under a vendor-looking scope, matching the dependency-confusion shape where a high version is used to win resolution against an internal package of the same name.\n",
"id": "MAL-2026-17631",
"modified": "2026-10-06T03:57:14Z",
"published": "2026-10-06T03:57:14Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@pinecone-experience/messages/v/99.9.1"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @pinecone-experience/messages (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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.