Which versions of @solana-js/web3 are malicious?

The following npm versions of @solana-js/web3 are flagged malicious: 1.91.3. Treat any of these as compromised.

How do I remediate @solana-js/web3 if I installed it?

@solana-js/web3 is a typosquat — you almost certainly intended a legitimately-named package. Remove @solana-js/web3, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @solana-js/web3 — how do I know if it already compromised me?

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

Yes — @solana-js/web3 is associated with the IN-MAL-2026-017665 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/web3 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-js/web3 (version 1.91.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @solana-js/web3 across your stack and pipelines.

Malicious package

@solana-js/web3npm

@solana-js/web3 is a confirmed malicious npm package (MAL-2026-13941) that typosquats a legitimate package to trick installs (malicious version 1.91.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @solana-js/web3 (npm)

MAL-2026-13941

Immediate action

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

npm uninstall @solana-js/web3

What this malware does

Package name @solana-js/web3 impersonates the legitimate @solana/web3.js SDK, and package.json falsely attributes authorship to 'Solana Labs' with a solana.com homepage. The exported API is a non-functional stub (Connection.getBalance returns 0, sendTransaction returns random bytes) — no real Solana client functionality is present. On install, scripts/postinstall.js detects Windows and spawns a hidden PowerShell (-NoP -W Hidden -Exec Bypass) with a base64-encoded command. The decoded PowerShell performs an AMSI bypass via reflection over System.Management.Automation.AmsiUtils, downloads a binary payload from https://files.catbox.moe/a3loxy.bin, and executes it in-process using VirtualAlloc/CreateThread. The postinstall script further hex-escapes API names ('child_process', 'powershell', 'platform', 'win32') and fragments the PowerShell payload to hinder review. The result is arbitrary remote code execution on any Windows host that runs npm install against this package, with the shellcode fetched from an anonymous, mutable file host (files.catbox.moe) — a known-bad-infrastructure dropper pattern.

Malicious versions

1 flagged

1.91.3

Indicators of compromise (SHA-256)

9b539591552f3e960f65ceb70d946bc56f240f9bdb1400c501723aa32fd305ec

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @solana-js/web3 (version 1.91.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @solana-js/web3 across your stack and pipelines.
If you installed it — respond
@solana-js/web3 is a typosquat — you almost certainly intended a legitimately-named package. Remove @solana-js/web3, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @solana-js/web3 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-js/web3 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-js/web3 on npm has been identified as a malicious package (version 1.91.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017665

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @solana-js/web3-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database