Which versions of solana-web3-lts are malicious?

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

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

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

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

Yes — solana-web3-lts is associated with the RLMA-2026-05623, IN-MAL-2026-012967, RLUA-2026-06504 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-lts 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-lts (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-lts across your stack and pipelines.

Malicious package

solana-web3-ltsnpm

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

MAL-2026-10901

Immediate action

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

npm uninstall solana-web3-lts

What this malware does

Package name 'solana-web3-lts' resembles the widely-used '@solana/web3.js' Solana SDK, raising name-confusion concerns for installers reaching for the official client. The shipped library bundles (lib/index.cjs.js, lib/index.esm.js) contain co-occurring use of child_process, fetch/POST/GET, and shell utilities (curl, ping) within large minified files; pattern-level signals match exfiltration shapes but full semantic tracing of the bundle did not complete, so it is not confirmed whether these primitives are reachable from an install/import path or are part of legitimate SDK functionality (e.g., RPC HTTP transports, build tooling). Recommend human review of the bundle to determine whether the child_process + network combination represents a hardcoded C2 exfiltration path or benign SDK code, and to confirm the package's relationship (if any) to the official Solana web3 client.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

17de020deed3039d0004c8c7d53de909c604e25b233c3e2ff6ab6586fa781967

51efd3d5cdcb8fb794a1702f586abd7018d86aad3e40286f5a43dd1127d804ed

73c314527cacf33dbf9e3853afe7c7f75e51e8137b2b09c4f5a89f27132bd68e

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-lts (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-lts across your stack and pipelines.
If you installed it — respond
solana-web3-lts 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-lts 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-lts 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-lts 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-05623IN-MAL-2026-012967RLUA-2026-06504

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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