Which versions of solana-web3-stable are malicious?

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

How do I remediate solana-web3-stable if I installed it?

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

If solana-web3-stable 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-web3-stable part of a known attack campaign?

Yes — solana-web3-stable is associated with the RLMA-2026-05625, IN-MAL-2026-012968, RLUA-2026-06506 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-web3-stable 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-web3-stable (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-web3-stable across your stack and pipelines.

Malicious package

solana-web3-stablenpm

solana-web3-stable is a confirmed malicious npm package (MAL-2026-10903) 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-web3-stable (npm)

MAL-2026-10903

Immediate action

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

npm uninstall solana-web3-stable

What this malware does

Package name 'solana-web3-stable' closely resembles the widely-used @solana/web3.js library, raising typosquat concern. The bundled lib/index.cjs.js and lib/index.esm.js contain co-located uses of child_process, hardcoded fetch/POST calls, and shell utilities (curl, ping). These keyword co-occurrences in a minified bundle are consistent with both a legitimate Solana client (which makes RPC POST/GET calls) and a malicious exfiltration shape; semantic verification of the actual call graph was not completed, so intent cannot be confirmed from the captured evidence alone. Routing to human review to confirm whether the network destinations are documented Solana RPC endpoints or attacker-controlled hosts, and whether child_process is invoked at install/import time.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d33636c7d2fa229e7bee4ff644f1d03218838c0960487798f54c542e33f6cf5e

38824d7f6044fd3177aba408a5f815879762d8829e56cb6692e2cad652f7d9e6

b2bae86a2f29592420e08ec7636e73c35a1b1957b699c2da97d2fa6a4c747e8e

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-web3-stable (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-web3-stable across your stack and pipelines.
If you installed it — respond
solana-web3-stable 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-web3-stable 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-web3-stable 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-web3-stable 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-05625IN-MAL-2026-012968RLUA-2026-06506

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks solana-web3-stable-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