MAL-2026-6278
Vulnerability from ossf_malicious_packages
Published
2026-06-23 06:22
Modified
2026-06-23 16:56
Summary
Malicious code in ts-wross (npm)
Details

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

Source: amazon-inspector (42dae43b7ff77748f10ae5faf6d87b7d63552e5629a37c931ea2c0de3539b469)

Package is published under the name ts-wross but its package.json claims authorship by Michael Mclaughlin (M8ch88l@gmail.com) and points its repository field at https://github.com/MikeMcl/big.js.git, with description and keywords copied from the legitimate big.js arbitrary-precision arithmetic library. The shipped source is a verbatim copy of big.js v7.0.1 with one modification: a try/catch block injected mid-file in both big.js and big.mjs that runs const doc = require("node-slot"); doc.from_str().then(...).catch(...) at module load. Errors are swallowed by the surrounding try/catch so the call is silent. node-slot is declared as a runtime dependency ("node-slot": "^1.0.8") and is therefore pulled in and executed on any require('ts-wross') / import 'ts-wross'. The legitimate big.js has zero dependencies and no such call — the inserted require is a loader trampoline that hands import-time execution on the installer's machine to whatever code node-slot ships. Combined with the impersonated metadata, the package is a lure that drops attacker-controlled code into any consumer that installs it under the assumption it is or relates to big.js.

Source: ghsa-malware (f2ee248f4b7fad7f6a978fbc5f1accf635566ce61a3ee32f1353eba91bbe42d6)

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.
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": "442c54a9b0beff03159cb7dd3a59ad1c09dbe09f0bcec91df0a33a032a2e4f99",
              "tlsh": "c6c2658c3ac67579593363788f465088eb38525712c8b286b4ae63b46f78cb107b5fdc"
            },
            {
              "path": "package.json",
              "sha256": "140bde4932b0284dafc5ca7d592ad54c2e07bdc6e3c9bd290c9f2de93718a6ec",
              "tlsh": "c0212677c9a19da70af89b947c6c03aaf1151b1f40a04c5bb07b130c4f3345b2095b7d"
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "ts-wross"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": [
        "0.0.8"
      ]
    }
  ],
  "aliases": [
    "GHSA-53h7-mc3v-w73c"
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "GHSA-53h7-mc3v-w73c",
        "import_time": "2026-06-23T07:33:18.913494656Z",
        "modified_time": "2026-06-23T06:22:06Z",
        "ranges": [
          {
            "events": [
              {
                "introduced": "0"
              }
            ],
            "type": "SEMVER"
          }
        ],
        "sha256": "f2ee248f4b7fad7f6a978fbc5f1accf635566ce61a3ee32f1353eba91bbe42d6",
        "source": "ghsa-malware"
      },
      {
        "id": "IN-MAL-2026-007271",
        "import_time": "2026-06-23T16:54:13.52835658Z",
        "modified_time": "2026-06-23T16:11:26Z",
        "sha256": "42dae43b7ff77748f10ae5faf6d87b7d63552e5629a37c931ea2c0de3539b469",
        "source": "amazon-inspector",
        "versions": [
          "0.0.8"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (42dae43b7ff77748f10ae5faf6d87b7d63552e5629a37c931ea2c0de3539b469)\nPackage is published under the name `ts-wross` but its package.json claims authorship by Michael Mclaughlin (M8ch88l@gmail.com) and points its repository field at https://github.com/MikeMcl/big.js.git, with description and keywords copied from the legitimate big.js arbitrary-precision arithmetic library. The shipped source is a verbatim copy of big.js v7.0.1 with one modification: a try/catch block injected mid-file in both `big.js` and `big.mjs` that runs `const doc = require(\"node-slot\"); doc.from_str().then(...).catch(...)` at module load. Errors are swallowed by the surrounding try/catch so the call is silent. `node-slot` is declared as a runtime dependency (`\"node-slot\": \"^1.0.8\"`) and is therefore pulled in and executed on any `require(\u0027ts-wross\u0027)` / `import \u0027ts-wross\u0027`. The legitimate big.js has zero dependencies and no such call \u2014 the inserted require is a loader trampoline that hands import-time execution on the installer\u0027s machine to whatever code `node-slot` ships. Combined with the impersonated metadata, the package is a lure that drops attacker-controlled code into any consumer that installs it under the assumption it is or relates to big.js.\n\n## Source: ghsa-malware (f2ee248f4b7fad7f6a978fbc5f1accf635566ce61a3ee32f1353eba91bbe42d6)\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-6278",
  "modified": "2026-06-23T16:56:09Z",
  "published": "2026-06-23T06:22:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-53h7-mc3v-w73c"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/ts-wross/v/0.0.8"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in ts-wross (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…