Malicious code in eth-library-toolkit (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13720
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (70d6b0e13b9995ecb7e5565f8515bdc8148d417fbb797e8a5bd12dcf0d7fbfff) [email protected] presents itself as @ethereumjs/util — README, badges, and the repository URL point at the ethereumjs/ethereumjs-monorepo — but is published under an unaffiliated npm account (azeura <[email protected]>). The package's dist/index.js unconditionally executes require("commonjs-assertion") at load time, and package.json declares "commonjs-assertion": "^1.2.7" as a runtime dependency in place of the upstream ethjs-util dependency used by the real @ethereumjs/util. commonjs-assertion is not an ethereumjs project and has no functional relationship to the utility APIs this package advertises. Any consumer that installs and requires eth-library-toolkit will resolve and execute whatever code commonjs-assertion currently ships, giving the substituted package arbitrary code execution inside the installer's Node.js process. The impersonation shell plus forced third-party dependency load matches the lookalike-clone-as-delivery-vehicle supply-chain pattern. ## Source: ghsa-malware (f0a14281d04c1441978bfb667f8ccb2a937f813404c0afff5dff33cb61b129cf) 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.
- Source published
- 10 Aug 2026 15:52:18 UTC
- Source modified
- 11 Aug 2026 12:30:12 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.