Summary
Togoder Security scanned the npm package eth-rpc-errors@4.0.3 on Oct 4, 2026. An AI review of 5 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
embedded_source_map
NPS-904CC2AF2D73
The file contains an inline base64-encoded source map in a comment. This is standard for compiled TypeScript output and not a security issue, but the encoded payload could theoretically obscure source data.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/classes.js | safe | This is a legitimate error-class implementation for Ethereum JSON-RPC errors (from @metamask/eth-rpc-errors style code) with no malicious patterns such as exfiltration, credential harvesting, code execution, or network activity. |
| dist/error-constants.js | safe | No malicious patterns detected; the file only defines static Ethereum/JSON-RPC error code constants and a benign inline source map. |
| dist/errors.js | safe | No malicious patterns detected; the file only defines Ethereum RPC and provider error helper functions with input validation. |
| dist/index.js | safe | No malicious patterns detected |
| dist/utils.js | safe | No malicious patterns detected; the file contains only error serialization utilities with no network, filesystem, process, or dynamic code execution behavior. |
Frequently asked questions
Is eth-rpc-errors safe to use?
Our AI source review of eth-rpc-errors@4.0.3 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does eth-rpc-errors contain malware?
No malware was identified in eth-rpc-errors@4.0.3 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was eth-rpc-errors checked?
Togoder Security downloaded the published npm package and had an AI model read its 5 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan eth-rpc-errors together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in eth-rpc-errors@4.0.3, cost nothing.