Which versions of solana-web3-patched are malicious?

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

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

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

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

Yes — solana-web3-patched is associated with the RLMA-2026-05624, IN-MAL-2026-012969, RLUA-2026-06505 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-patched 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-patched (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-patched across your stack and pipelines.

Malicious package

solana-web3-patchednpm

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

MAL-2026-10902

Immediate action

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

npm uninstall solana-web3-patched

What this malware does

Package name 'solana-web3-patched' resembles the legitimate '@solana/web3.js' library and is published as an unscoped lookalike at version 1.0.0. The bundled lib/index.cjs.js and lib/index.esm.js contain co-occurring patterns of child_process import, fetch/POST/GET calls, and shell utilities (curl, ping) within the same files. Pattern matches alone in a minified/bundled file cannot conclusively distinguish legitimate Solana RPC client behavior from exfiltration, and traced-code corroboration is unavailable. Given the typosquat-shaped name plus presence of child_process + outbound HTTP + curl/ping primitives in the bundle, the package warrants human review before allowing into installer environments. A reviewer should verify whether the child_process and curl/ping references are reachable at require/install time and whether any hardcoded destinations are attacker-controlled.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

13702864205b5765c6d58ae6826703e1368c2fefa58e7220ff983af4f1956dea

e99e6f959c8df3e2933c860ba3d36dc5dbbd27d97a69a3e97a5a7feaf7e24899

3b78ec8bd31aee7c11ed93989d76308c36496b53f9eda8683953edd1cba69219

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-patched (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-patched across your stack and pipelines.
If you installed it — respond
solana-web3-patched 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-patched 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-patched 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-patched 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-05624IN-MAL-2026-012969RLUA-2026-06505

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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