Malicious code in eth-lib-utils (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (13895e2e8ee4aa9683c2fd6f0f873a38b19bbc5af207233e22c51668bc7dba41) Package [email protected] impersonates @ethereumjs/util / ethereumjs-util (README, author list, repository URL, and source tree copied from the legitimate package). The published Node build dist/index.js contains an unconditional `require("assertcore")` at module load that is absent from the TypeScript source src/index.ts and from the parallel dist.browser/index.js — the import was injected only into the shipped artifact. The required name `assertcore` is not declared in package.json; the declared dependency is the differently-named `assertcoreutils` (^2.3.2), an unrelated name shaped to look like an Ethereum companion package. The effect on a consumer that runs `require('eth-lib-utils')` in Node is to load whatever code is published under `assertcore` / `assertcoreutils` in the installer's process, while the package presents itself as a drop-in for a widely-used Ethereum utility. This is the standard typosquat-plus-transitive-dropper shape: the lure package looks like a clean re-export, the harmful code lives one resolution hop away in a name the installer never asked for. ## Source: ghsa-malware (589c50080d1bc6f3f4325e1cd580084f98378fbfced6109dbcbba5fefc0b14d7) 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.
AI Analysis
Technical Summary
The eth-lib-utils npm package versions 5.2.3, 5.2.4, and 5.2.5 are malicious typosquatting packages impersonating ethereumjs-util. They include an injected require('assertcore') in the Node.js build artifact that is absent from the source code and browser build. The assertcore package is not declared in package.json, differing from the declared dependency assertcoreutils, and is used to execute malicious code when eth-lib-utils is imported in Node.js. This attack leverages a transitive dependency to drop harmful code unnoticed by consumers expecting a legitimate Ethereum utility package.
Potential Impact
Consumers who install and require eth-lib-utils versions 5.2.3, 5.2.4, or 5.2.5 in Node.js environments will inadvertently execute code from the malicious assertcore package. This can lead to arbitrary code execution within the installer's process. The package is designed to appear as a legitimate Ethereum utility, increasing the risk of unsuspecting developers incorporating it into their projects.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing eth-lib-utils versions 5.2.3, 5.2.4, and 5.2.5. Verify the authenticity of Ethereum utility packages by checking package names carefully to avoid typosquatting. Consider using trusted package sources and integrity verification mechanisms. Monitor vendor advisories for updates or official fixes regarding this malicious package.
Malicious code in eth-lib-utils (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (13895e2e8ee4aa9683c2fd6f0f873a38b19bbc5af207233e22c51668bc7dba41) Package [email protected] impersonates @ethereumjs/util / ethereumjs-util (README, author list, repository URL, and source tree copied from the legitimate package). The published Node build dist/index.js contains an unconditional `require("assertcore")` at module load that is absent from the TypeScript source src/index.ts and from the parallel dist.browser/index.js — the import was injected only into the shipped artifact. The required name `assertcore` is not declared in package.json; the declared dependency is the differently-named `assertcoreutils` (^2.3.2), an unrelated name shaped to look like an Ethereum companion package. The effect on a consumer that runs `require('eth-lib-utils')` in Node is to load whatever code is published under `assertcore` / `assertcoreutils` in the installer's process, while the package presents itself as a drop-in for a widely-used Ethereum utility. This is the standard typosquat-plus-transitive-dropper shape: the lure package looks like a clean re-export, the harmful code lives one resolution hop away in a name the installer never asked for. ## Source: ghsa-malware (589c50080d1bc6f3f4325e1cd580084f98378fbfced6109dbcbba5fefc0b14d7) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The eth-lib-utils npm package versions 5.2.3, 5.2.4, and 5.2.5 are malicious typosquatting packages impersonating ethereumjs-util. They include an injected require('assertcore') in the Node.js build artifact that is absent from the source code and browser build. The assertcore package is not declared in package.json, differing from the declared dependency assertcoreutils, and is used to execute malicious code when eth-lib-utils is imported in Node.js. This attack leverages a transitive dependency to drop harmful code unnoticed by consumers expecting a legitimate Ethereum utility package.
Potential Impact
Consumers who install and require eth-lib-utils versions 5.2.3, 5.2.4, or 5.2.5 in Node.js environments will inadvertently execute code from the malicious assertcore package. This can lead to arbitrary code execution within the installer's process. The package is designed to appear as a legitimate Ethereum utility, increasing the risk of unsuspecting developers incorporating it into their projects.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing eth-lib-utils versions 5.2.3, 5.2.4, and 5.2.5. Verify the authenticity of Ethereum utility packages by checking package names carefully to avoid typosquatting. Consider using trusted package sources and integrity verification mechanisms. Monitor vendor advisories for updates or official fixes regarding this malicious package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10499
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff9068715ace432f4b25
Added to database: 07/14/2026, 09:21:20 UTC
Last enriched: 07/14/2026, 09:48:48 UTC
Last updated: 07/30/2026, 07:53:30 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.