MAL-2026-6325
Vulnerability from ossf_malicious_packages
Published
2026-06-23 15:55
Modified
2026-06-23 15:55
Summary
Malicious code in web3-eth-util (npm)
Details

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

Source: amazon-inspector (f2e70ad91037bdc97e6b1ab8c95f5f2b5eecdb4524582d79dae5f240cbdbfc29)

Package name and metadata impersonate the legitimate @ethereumjs/util / ethereumjs-util packages: README is copied verbatim from the upstream ethereumjs project (and even instructs users to npm install eth-util), the contributor list and repository URL point at ethereumjs/ethereumjs-monorepo, but the package is published under a different name and ownership. The published dist/index.js (line ~57) contains require("assertcore") and package.json declares "assertcore": "^3.1.7" as a runtime dependency. The human-authored src/index.ts has no such import, and the browser build at dist.browser/index.js also omits it — the extra require is injected only into the Node-targeted build that ships in the npm tarball, so reviewers reading the GitHub source see clean code while npm install + require('web3-eth-util') silently loads the third-party 'assertcore' package in the consumer's Node process with full privileges. 'assertcore' is not part of the legitimate @ethereumjs/util sources and resembles a typosquat of the standard 'assert' module. The combination — brand impersonation of a widely used Ethereum utility package, source/dist divergence hiding the injection from GitHub readers, and a require-time pull of an unrelated third-party package — is a dependency-chain dropper pattern that delivers attacker-controlled code to anyone who installs and imports this package.

CWE
  • 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"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "dist/index.js",
              "sha256": "b58ae60ae0836b1569599e7f53790f6a70bb1ecd60e5b1232b5c76361c0afa22",
              "tlsh": "8a51cc1b3658b8f583f860f81b2bd1c3f931593301b29a24866cd7f0dda698a85f4e1d"
            }
          ],
          "package_integrity": [
            {
              "filename": "web3-eth-util-6.2.8.tgz",
              "hashes": {
                "sha1": "e279959e4dd88d28e1ed1054565971ef83faef12",
                "sha512_sri": "sha512-bk1Kn2+1lGeQkU/XKwnb3mixK6yzYz7leYHvjLsnuwQonW19Z15TjEpoH4RvzJPDjEZbWkK5WBXkppxGRhwqtQ=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "web3-eth-util"
      },
      "versions": [
        "6.2.8"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-007254",
        "import_time": "2026-06-23T16:54:11.947277221Z",
        "modified_time": "2026-06-23T15:55:58Z",
        "sha256": "f2e70ad91037bdc97e6b1ab8c95f5f2b5eecdb4524582d79dae5f240cbdbfc29",
        "source": "amazon-inspector",
        "versions": [
          "6.2.8"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f2e70ad91037bdc97e6b1ab8c95f5f2b5eecdb4524582d79dae5f240cbdbfc29)\nPackage name and metadata impersonate the legitimate @ethereumjs/util / ethereumjs-util packages: README is copied verbatim from the upstream ethereumjs project (and even instructs users to `npm install eth-util`), the contributor list and repository URL point at ethereumjs/ethereumjs-monorepo, but the package is published under a different name and ownership. The published dist/index.js (line ~57) contains `require(\"assertcore\")` and package.json declares `\"assertcore\": \"^3.1.7\"` as a runtime dependency. The human-authored src/index.ts has no such import, and the browser build at dist.browser/index.js also omits it \u2014 the extra require is injected only into the Node-targeted build that ships in the npm tarball, so reviewers reading the GitHub source see clean code while `npm install` + `require(\u0027web3-eth-util\u0027)` silently loads the third-party \u0027assertcore\u0027 package in the consumer\u0027s Node process with full privileges. \u0027assertcore\u0027 is not part of the legitimate @ethereumjs/util sources and resembles a typosquat of the standard \u0027assert\u0027 module. The combination \u2014 brand impersonation of a widely used Ethereum utility package, source/dist divergence hiding the injection from GitHub readers, and a require-time pull of an unrelated third-party package \u2014 is a dependency-chain dropper pattern that delivers attacker-controlled code to anyone who installs and imports this package.\n",
  "id": "MAL-2026-6325",
  "modified": "2026-06-23T15:55:58Z",
  "published": "2026-06-23T15:55:58Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/web3-eth-util/v/6.2.8"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in web3-eth-util (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…