# eth-rpc-errors@4.0.3 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-04T16:29:43.000Z
- Files reviewed: 5
- Findings: 1 low severity finding
- Report: https://security.togoder.click/npm/eth-rpc-errors
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## 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

### [low] embedded_source_map

Finding ID: `NPS-904CC2AF2D73`

File: `dist/classes.js:95`

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

- `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.

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology