Summary
Togoder Security scanned the npm package @metamask/json-rpc-engine@7.3.3 on Oct 4, 2026. An AI review of 7 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/JsonRpcEngine.js | safe | No malicious patterns detected; the code is a standard JSON-RPC engine implementation from MetaMask with no suspicious behavior. |
| dist/createAsyncMiddleware.js | safe | No malicious patterns detected; the code is a standard async middleware wrapper with no network, filesystem, process, or obfuscation activity. |
| dist/createScaffoldMiddleware.js | safe | No malicious patterns detected |
| dist/getUniqueId.js | safe | No malicious patterns detected; the code is a simple unique ID generator with no network, filesystem, process, or obfuscation concerns. |
| dist/idRemapMiddleware.js | safe | No malicious patterns detected |
| dist/index.js | safe | No malicious patterns detected; this is a standard TypeScript-compiled barrel file re-exporting local middleware modules. |
| dist/mergeMiddleware.js | safe | No malicious patterns detected in mergeMiddleware.js; it simply composes a middleware stack using a local JsonRpcEngine module. |
Affected version ranges
None of the 2 scanned versions of @metamask/json-rpc-engine are flagged high or critical. The latest scanned version, 11.0.0, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 9.0.3 – 11.0.0 | Not scanned | 3 | >=9.0.3 <=11.0.0 | |
| 7.3.3 – 8.0.2 | No issues | 2 | >=7.3.3 <=8.0.2 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @metamask/json-rpc-engine
Frequently asked questions
Is @metamask/json-rpc-engine safe to use?
Our AI source review of @metamask/json-rpc-engine@7.3.3 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @metamask/json-rpc-engine contain malware?
No malware was identified in @metamask/json-rpc-engine@7.3.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 @metamask/json-rpc-engine checked?
Togoder Security downloaded the published npm package and had an AI model read its 7 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/json-rpc-engine 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/json-rpc-engine@7.3.3, cost nothing.