Which versions of solana-web3-fixed are malicious?

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

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

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

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

Yes — solana-web3-fixed is associated with the RLMA-2026-05621, IN-MAL-2026-012966, RLUA-2026-06502 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-fixed 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-fixed (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-fixed across your stack and pipelines.

Malicious package

solana-web3-fixednpm

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

MAL-2026-10899

Immediate action

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

npm uninstall solana-web3-fixed

What this malware does

Package name 'solana-web3-fixed' resembles a fix-branded variant of the legitimate '@solana/web3.js' library, a pattern frequently used in lure/typosquat campaigns. The bundled main files (lib/index.cjs.js and lib/index.esm.js) trigger multiple keyword co-occurrence patterns associated with credential exfiltration: require('child_process') alongside POST/GET fetch calls and shell utilities (curl, ping). Without traced-code corroboration, these patterns cannot be conclusively attributed to either malicious behavior or legitimate Solana RPC / build tooling composition inside a minified bundle. Given the high-risk naming pattern (fix-branded variant of a top-tier crypto library) and the stacked critical static signals across both CJS and ESM bundles, this should be reviewed by a human before being trusted in any installer pipeline.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

213a28e690408d4d3356af127ab0c98a9d663a390c9ab07a980459ea9644ca3b

2d36c0e75143828e4a93135d0c54fb34dd6e75588a493ade663a1fa4b231230c

51b6e0a86bdacbadc2271559f93ff7173c6d5a1fcaaa0b6514db59a819099d6c

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-fixed (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-fixed across your stack and pipelines.
If you installed it — respond
solana-web3-fixed 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-fixed 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-fixed 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-fixed 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-05621IN-MAL-2026-012966RLUA-2026-06502

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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