mal-2026-15560
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (ab1df02839294b29ff278b7a80505be50de75eb0f317f4bf29635236a75e4b15)
The published dist/ bundles (main/module/browser entrypoints) contain code absent from the src/ tree: at library load they read an encrypted rsaToken from a package file via readRSAFromPackage(), DES-decrypt it using a key imported from the dependency manager-thedate, and pipe the plaintext into child_process.spawn('node', [],...) via stdin, executing the decrypted JavaScript in the installer's Node process. The DES key dependency is declared as "manager-thedate": "latest" in package.json, so the effective payload can be changed at any time by whoever controls that dependency, even though supersignaturenature itself is version-pinned. The src/ tree implements a straightforward Theta blockchain client with no fs, child_process, DES, or spawn usage; the shipped dist/*.js contains var child_process = require('child_process'), function decryptToken(token, password) using CryptoJS.DES.decrypt, readRSAFromPackage, and rsa_exec.stdin.write(String(rsaDecrypted)) against a spawned node process. The runtime code is not a rollup of the shipped source, so review of src/ does not reveal the loader that consumers actually execute.
Source: ghsa-malware (5004322b8287b46b1d08bb827df71af4a4f723d8a4b88c25beca9f7709d5e7d2)
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"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "dist/supersignaturenature.esm.js",
"sha256": "728e2f4f054de13c9de5bbf8f8c010c4941402e254fcde43458240f39c70035e",
"tlsh": "5563949d26e7a060815b70b56fdb94407129e00b68ccd82cbdac53958fd946c9bf2ff8"
},
{
"path": "dist/supersignaturenature.cjs.js",
"sha256": "7776d30e6fe4073e6bbf09c93e7ae92f1b2109dd8543683fb3aeb5ccb6d76679",
"tlsh": "cf63939d26e7a060815b70b56fdb94407129e00b68ccd82cbdac53958fd946c9bf2ff8"
},
{
"path": "src/index.js",
"sha256": "2cdcb24d14af30ebda4c3dc548128d112790c00ad57c46b32972f828f9bcf0ce",
"tlsh": "9f01f7762ca68730813508c0764f282542f5e3137fa434a863672334cbc988dacac49b"
},
{
"path": "package.json",
"sha256": "f508b2ef4daed69216e1face0a1f6e8121b961a32a8809a417e9b097ded0ccf1",
"tlsh": "a8310d24cf24cdb345c825b9282a4547676988874c46f86c33954b4e4f4e27f22fa7be"
}
],
"package_integrity": [
{
"filename": "supersignaturenature-1.0.5.tgz",
"hashes": {
"sha1": "c60ccc5333563e7f1ac1b4bb00aa6f4ccc72f3c4",
"sha512_sri": "sha512-91qk/Pt0yTfBFHnOV4Q/aUgmRQqsmPL4jSBH6S1Oz3ThIA+wtmQng+D1ABVbITZF6lP3cIfISprJBpbEi0qi8Q=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "supersignaturenature"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"1.0.5",
"1.0.6"
]
}
],
"aliases": [
"GHSA-x67q-xvcf-f2rw"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019144",
"import_time": "2026-08-29T02:22:21.400369521Z",
"modified_time": "2026-08-29T02:14:39Z",
"sha256": "16a45a7d4dd29a1780c37baa5b8508bea099660b71193d6b6a30ef02edaf37ca",
"source": "amazon-inspector",
"versions": [
"1.0.5"
]
},
{
"id": "IN-MAL-2026-019146",
"import_time": "2026-08-29T02:22:21.5860358Z",
"modified_time": "2026-08-29T02:14:55Z",
"sha256": "ab1df02839294b29ff278b7a80505be50de75eb0f317f4bf29635236a75e4b15",
"source": "amazon-inspector",
"versions": [
"1.0.6"
]
},
{
"id": "GHSA-x67q-xvcf-f2rw",
"import_time": "2026-08-29T20:22:41.209908964Z",
"modified_time": "2026-08-29T19:26:32Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "5004322b8287b46b1d08bb827df71af4a4f723d8a4b88c25beca9f7709d5e7d2",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (ab1df02839294b29ff278b7a80505be50de75eb0f317f4bf29635236a75e4b15)\nThe published dist/ bundles (main/module/browser entrypoints) contain code absent from the src/ tree: at library load they read an encrypted rsaToken from a package file via readRSAFromPackage(), DES-decrypt it using a key imported from the dependency manager-thedate, and pipe the plaintext into child_process.spawn(\u0027node\u0027, [],...) via stdin, executing the decrypted JavaScript in the installer\u0027s Node process. The DES key dependency is declared as \"manager-thedate\": \"latest\" in package.json, so the effective payload can be changed at any time by whoever controls that dependency, even though supersignaturenature itself is version-pinned. The src/ tree implements a straightforward Theta blockchain client with no fs, child_process, DES, or spawn usage; the shipped dist/*.js contains var child_process = require(\u0027child_process\u0027), function decryptToken(token, password) using CryptoJS.DES.decrypt, readRSAFromPackage, and rsa_exec.stdin.write(String(rsaDecrypted)) against a spawned node process. The runtime code is not a rollup of the shipped source, so review of src/ does not reveal the loader that consumers actually execute.\n\n## Source: ghsa-malware (5004322b8287b46b1d08bb827df71af4a4f723d8a4b88c25beca9f7709d5e7d2)\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-15560",
"modified": "2026-08-29T20:24:29.660847086Z",
"published": "2026-08-29T02:14:39Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/supersignaturenature/v/1.0.5"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/supersignaturenature/v/1.0.6"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-x67q-xvcf-f2rw"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in supersignaturenature (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.