mal-2026-6574
Vulnerability from ossf_malicious_packages
Published
2026-06-29 04:17
Modified
2026-08-21 12:28
Summary
Malicious code in yandex-geobase (npm)
Details
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (1f6219d513896736aee31ce33719d6ae2d1f5b03293ecdfe884d944bbb3eb99a)
yandex-geobase@3.9.0 squats the internal-sounding name 'yandex-geobase' and ships a postinstall script that performs an HTTP GET to a hardcoded bare-IP endpoint (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) on every install. The beacon transmits the package name, version, and a campaign identifier, confirming successful code execution inside the installer's build environment to a third-party host. The package self-describes as a 'Dependency confusion security test placeholder', but a self-label of 'PoC' does not change the installer-facing behavior: any build pipeline that resolves this public name in place of an internal Yandex package will silently signal an external bare-IP host that attacker-controlled code ran inside the installer's environment. The destination is a bare IP on a non-standard port (not a registry, vendor domain, or telemetry endpoint), which is consistent with dependency-confusion canary infrastructure rather than legitimate package behavior.
Source: ghsa-malware (82d597d93ff0385acef350ebc8330d88eaf5756b7e516b4ca006ae72850f87dd)
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.
CWE
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
Credits
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "postinstall.js",
"sha256": "abd78197cda15359797c65c76ea96b3bd7f20b047e18a9cd68d978ea9fa38353",
"tlsh": "4ce0237849f040251dea8484f393685b95cbd142f065f580fd8e12901fd395366631f0"
}
],
"package_integrity": [
{
"filename": "yandex-geobase-2.9.0.tgz",
"hashes": {
"sha1": "3df4f6f89f7e50a6c2f296fb5c5b19d00085f46e",
"sha512_sri": "sha512-/WGapuOJYcIFNxLMDF6HRQSSEQAkCGINp4Jm4Fmn+yQFaZ4jg2LqqUMi9+hq0M5Azrgnm46z/95Cj4BKfRuCuw=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "yandex-geobase"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"2.9.0",
"2.1.2",
"3.9.0",
"2.1.0",
"2.2.0",
"2.1.1"
]
}
],
"aliases": [
"GHSA-86q5-cfp8-j54g"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-007720",
"import_time": "2026-06-29T05:07:06.783736481Z",
"modified_time": "2026-06-29T04:18:25Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "1afe70f3f7794a4ef230823c92bc635e3fd70c82342bd41c1df1bbcd6105a8ea",
"source": "amazon-inspector",
"versions": [
"2.9.0"
]
},
{
"id": "IN-MAL-2026-007716",
"import_time": "2026-06-29T05:07:06.188445637Z",
"modified_time": "2026-06-29T04:17:52Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "cc198965d3b086a519c0027b94c392f00c6ab0246feb11694af1c43b12236a70",
"source": "amazon-inspector",
"versions": [
"2.1.2"
]
},
{
"id": "IN-MAL-2026-007717",
"import_time": "2026-06-29T05:07:06.295402289Z",
"modified_time": "2026-06-29T04:18:00Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "1f6219d513896736aee31ce33719d6ae2d1f5b03293ecdfe884d944bbb3eb99a",
"source": "amazon-inspector",
"versions": [
"3.9.0"
]
},
{
"id": "IN-MAL-2026-007719",
"import_time": "2026-06-29T05:07:06.645863701Z",
"modified_time": "2026-06-29T04:18:18Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "69bb1d25ef0863fb16ce33e0536266243a6e007fa71d36303205fb0f8d71c110",
"source": "amazon-inspector",
"versions": [
"2.1.0"
]
},
{
"id": "IN-MAL-2026-007718",
"import_time": "2026-06-29T05:07:06.465324577Z",
"modified_time": "2026-06-29T04:18:07Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "a16ea7792b5f438d3338f62a9d3d801c7e30892f1da7c75e0f9fd4e93af4c047",
"source": "amazon-inspector",
"versions": [
"2.2.0"
]
},
{
"id": "IN-MAL-2026-008882",
"import_time": "2026-07-08T22:51:31.376711603Z",
"modified_time": "2026-07-08T22:47:04Z",
"sha256": "ff9900918ba51446fba8f3ea7e861879123d55c7e86f5d82c886a57c8f0572ec",
"source": "amazon-inspector",
"versions": [
"2.1.1"
]
},
{
"id": "GHSA-86q5-cfp8-j54g",
"import_time": "2026-08-21T12:26:03.444158926Z",
"modified_time": "2026-08-21T11:53:39Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "82d597d93ff0385acef350ebc8330d88eaf5756b7e516b4ca006ae72850f87dd",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (1f6219d513896736aee31ce33719d6ae2d1f5b03293ecdfe884d944bbb3eb99a)\nyandex-geobase@3.9.0 squats the internal-sounding name \u0027yandex-geobase\u0027 and ships a postinstall script that performs an HTTP GET to a hardcoded bare-IP endpoint (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) on every install. The beacon transmits the package name, version, and a campaign identifier, confirming successful code execution inside the installer\u0027s build environment to a third-party host. The package self-describes as a \u0027Dependency confusion security test placeholder\u0027, but a self-label of \u0027PoC\u0027 does not change the installer-facing behavior: any build pipeline that resolves this public name in place of an internal Yandex package will silently signal an external bare-IP host that attacker-controlled code ran inside the installer\u0027s environment. The destination is a bare IP on a non-standard port (not a registry, vendor domain, or telemetry endpoint), which is consistent with dependency-confusion canary infrastructure rather than legitimate package behavior.\n\n## Source: ghsa-malware (82d597d93ff0385acef350ebc8330d88eaf5756b7e516b4ca006ae72850f87dd)\nAny 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.\n",
"id": "MAL-2026-6574",
"modified": "2026-08-21T12:28:13.650255822Z",
"published": "2026-06-29T04:17:52Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/2.9.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/2.1.2"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/3.9.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/2.1.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/2.2.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/yandex-geobase/v/2.1.1"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-86q5-cfp8-j54g"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in yandex-geobase (npm)"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
Loading…