Which versions of solana-rpc-client are malicious?

The following npm versions of solana-rpc-client are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate solana-rpc-client if I installed it?

solana-rpc-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed solana-rpc-client — how do I know if it already compromised me?

If solana-rpc-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is solana-rpc-client part of a known attack campaign?

Yes — solana-rpc-client is associated with the RLMA-2026-05618, IN-MAL-2026-013034, RLUA-2026-06499 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find solana-rpc-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solana-rpc-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-rpc-client across your stack and pipelines.

Malicious package

solana-rpc-clientnpm

solana-rpc-client is a confirmed malicious npm package (MAL-2026-10898) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solana-rpc-client (npm)

MAL-2026-10898

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall solana-rpc-client

What this malware does

The package's bundled entry points (lib/index.cjs.js and lib/index.esm.js) co-locate require('child_process'), fetch/POST/GET calls, and references to curl/ping within minified output. The package name suggests a Solana RPC client, which would legitimately make HTTP/RPC calls; keyword co-occurrence in a minified bundle is consistent with both that legitimate shape and an exfiltration shape, and the available evidence does not show the destination URLs, whether any code path runs at install/import time, or whether process.env or credential paths feed any of the network calls. No package.json lifecycle hook content has been confirmed. Routing to human review so a reviewer can de-minify the relevant spans (around lines 5016/5046, 11212/11317) and confirm whether the network destinations are documented Solana RPC endpoints (allow) or attacker-controlled hosts (escalate to block).

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f0865d9a18dba082e66e2981a223c0b419e064bf492646d747e428cab64787c5

e57e3e79e60f9b8ec7f7c9b5199ecab2efaf72566eaed0f358a3b80adad5558d

c4525132bdbb768eeadd139d212b0c7355077a54f4158483435faa65b3047b2e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solana-rpc-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-rpc-client across your stack and pipelines.
If you installed it — respond
solana-rpc-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If solana-rpc-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks solana-rpc-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. solana-rpc-client on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05618IN-MAL-2026-013034RLUA-2026-06499

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks solana-rpc-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database