Summary
Togoder Security scanned the npm package @metamask/rpc-errors@6.4.0 on Oct 4, 2026. An AI review of 10 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/classes.cjs | safe | No malicious patterns detected |
| dist/classes.mjs | safe | No malicious patterns detected; the code is a standard JSON-RPC error implementation with safe imports from trusted packages and no network, filesystem, process, or dynamic code execution concerns. |
| dist/error-constants.cjs | safe | No malicious patterns detected; the file only defines static error code constants and messages for JSON-RPC/EIP standards. |
| dist/error-constants.mjs | safe | Cleared by Jev triage; no further analysis needed |
| dist/errors.cjs | safe | No malicious patterns detected; the file only defines JSON-RPC and Ethereum provider error constructors with no network, filesystem, process, or dynamic code execution behavior. |
| dist/errors.mjs | safe | Cleared by Jev triage; no further analysis needed |
| dist/index.cjs | safe | No malicious patterns detected in this simple re-export module. |
| dist/index.mjs | safe | No malicious patterns detected |
| dist/utils.cjs | safe | No malicious patterns detected |
| dist/utils.mjs | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 2 scanned versions of @metamask/rpc-errors are flagged high or critical. The latest scanned version, 7.0.3, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 7.0.3 | Not scanned | 1 | 7.0.3 | |
| 6.4.0 – 7.0.2 | No issues | 2 | >=6.4.0 <=7.0.2 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @metamask/rpc-errors
Frequently asked questions
Is @metamask/rpc-errors safe to use?
Our AI source review of @metamask/rpc-errors@6.4.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @metamask/rpc-errors contain malware?
No malware was identified in @metamask/rpc-errors@6.4.0 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 @metamask/rpc-errors checked?
Togoder Security downloaded the published npm package and had an AI model read its 10 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 @metamask/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 @metamask/rpc-errors@6.4.0, cost nothing.