@solana-labs/etherjsnpm
Advisory published Updated
@solana-labs/etherjs is a confirmed malicious npm package (MAL-2026-5362) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.5, 1.0.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @solana-labs/etherjs (npm)
What this malware does
Package is published as @solana-labs/etherjs but its README documents itself as @solana-labs/web3.js and instructs consumers to import { Connection, PublicKey, Keypair } from '@solana-labs/web3.js' — the legitimate Solana SDK is @solana/web3.js (no -labs). Developers who copy the README install line land on this package instead. The Node CommonJS and ESM bundles (lib/index.cjs.js, lib/index.esm.js) are a fork of solana-web3.js with an injected payload that, on require()/import, reads process.env (lines 11365-11366, 11448, 11453, 11542, 11547 in the CJS bundle) and POSTs the harvested data to a hardcoded bare IP http://104.239.66.223:8899 (line 11384) and to https://api.telegram.org/bot.../sendMessage with a fixed chat_id (lines 11415-11417). The same blocks repeatedly require('child_process') (lines 11441, 11466, 11479, 11495, 11535) and invoke curl, enabling attacker-influenced shell execution on the installer host. The browser/native bundles omit the payload, confirming it is gated to Node consumers. Both attacker destinations are hardcoded with no opt-out.
The OpenSSF Package Analysis project identified '@solana-labs/etherjs' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @solana-labs/etherjs (8 malicious versions).
If you installed it — respond
@solana-labs/etherjs 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-labs/etherjs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @solana-labs/etherjs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.