Which versions of solana-js-client are malicious?

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

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

solana-js-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-js-client — how do I know if it already compromised me?

If solana-js-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — solana-js-client is associated with the IN-MAL-2026-006745, RLMA-2026-05616, RLUA-2026-06497 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-js-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for solana-js-client (version 1.0.0).

Malicious package

solana-js-clientnpm

Advisory published Jun 16, 2026Updated Sep 1, 2026

solana-js-client is a confirmed malicious npm package (MAL-2026-5860) 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-js-client (npm)

MAL-2026-5860

Immediate action

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

npm uninstall solana-js-client

What this malware does

Package masquerades as a 'Drop-in replacement for @solana/web3.js' and lists its author as 'Solana Labs Maintainers [email protected]' to impersonate the legitimate Solana Labs publisher. The published bundles lib/index.cjs.js and lib/index.esm.js contain an injected payload at the tail of the file with no counterpart in src/. The payload requires child_process, shells out via curl/ping, and references a hardcoded plain-HTTP endpoint http://104.239.66.223:8899 (port 8899 is the Solana JSON-RPC port) along with Telegram Bot API sendMessage URLs carrying a chat_id controlled by the attacker. Because the package's primary API is the Connection class, any consumer wallet or dApp that imports this drop-in replacement can have its outbound RPC traffic, signed transactions, or seed material silently rerouted to the attacker-owned RPC and exfiltrated to the attacker's Telegram bot. Indicators: rogue RPC at 104.239.66.223:8899; exfiltration channel via api.telegram.org/bot<redacted>/sendMessage.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

855cf386497f33e21db48ae8b87c769fd777f52b585f3d8d5f276fd4c9d42628

8f10d8377c8f930a42c2ee233bf542b8b6e4eecf4c80763d3155bb8c214c71cb

6fbcc6c5e1265acef5047058294565b8bd60c02cceabf088d1930b561c5f12b9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for solana-js-client (version 1.0.0).
If you installed it — respond
solana-js-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-js-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. solana-js-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

IN-MAL-2026-006745RLMA-2026-05616RLUA-2026-06497

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks solana-js-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