Summary
Togoder Security scanned the npm package @solana/rpc-transport-http@5.0.0 on Oct 4, 2026. An AI review of 5 source files produced 3 low severity findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 3
environment variable access
NPS-20FACBCF5674
Reads process.env.NODE_ENV to conditionally enable development-mode header validation warnings. This is standard practice and not credential harvesting.
network request
NPS-4861300FFBE0
The code performs HTTP POST requests to a user-configured RPC URL via fetch. This is expected behavior for a Solana RPC HTTP transport and does not constitute exfiltration.
Header Validation Logic
NPS-C2769E4A426A
The code implements a header validation function that blocks forbidden HTTP headers (e.g., cookie, host, proxy-*, sec-*). This is a security feature, not a vulnerability. However, it only runs in non-production environments (process.env.NODE_ENV !== 'production'), which may allow header injection in production if custom headers are user-controlled. This is a low-severity design consideration, not a malicious pattern.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/index.browser.cjs | safe | No malicious patterns detected; the code is a legitimate HTTP transport implementation for Solana RPC with proper header validation and no exfiltration, credential harvesting, or dynamic code execution. |
| dist/index.browser.mjs | safe | No malicious patterns detected; the code is a legitimate Solana RPC HTTP transport implementation with proper header validation and no exfiltration, credential harvesting, or dynamic code execution. |
| dist/index.native.mjs | safe | The code is a legitimate Solana RPC HTTP transport implementation with no malicious patterns; it only makes user-configured RPC requests. |
| dist/index.node.cjs | safe | No malicious patterns detected; the code is a standard Solana RPC HTTP transport implementation with only defensive header validation and no exfiltration, credential harvesting, obfuscation, or backdoor behavior. |
| dist/index.node.mjs | safe | The code is a legitimate Solana RPC HTTP transport client with no malicious patterns; it performs standard JSON-RPC requests and includes header validation as a security measure. |
Affected version ranges
None of the 2 scanned versions of @solana/rpc-transport-http are flagged high or critical. The latest scanned version, 5.0.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 3.0.3 – 5.0.0 | No issues | 2 | >=3.0.3 <=5.0.0 | |
| 2.1.1 | Not scanned | 1 | 2.1.1 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @solana/rpc-transport-http
Frequently asked questions
Is @solana/rpc-transport-http safe to use?
Our AI source review of @solana/rpc-transport-http@5.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @solana/rpc-transport-http contain malware?
No malware was identified in @solana/rpc-transport-http@5.0.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 @solana/rpc-transport-http 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 @solana/rpc-transport-http 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 @solana/rpc-transport-http@5.0.0, cost nothing.