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

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

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

@wethenorth12/solana-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.

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

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

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

Malicious package

@wethenorth12/solana-web3npm

@wethenorth12/solana-web3 is a confirmed malicious npm package (MAL-2026-12102) that steals credentials and exfiltrates sensitive data (malicious version 2.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12102

Immediate action

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

npm uninstall @wethenorth12/solana-web3

What this malware does

On require of the package's main entry (index.js), the code collects process.env, hostname, username, homedir, platform, cwd and a timestamp, JSON-encodes and base64-encodes the payload, and sends it via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id 8969499041. A tmp flag file is used to suppress repeat sends. The payload includes the full process.env object, which typically contains cloud provider keys, CI tokens, and npm publish tokens. The package name @wethenorth12/solana-web3 mimics @solana/web3.js, package.json forges the author as 'solana-labs' with a spoofed github.com/solana-labs repository URL, and the README markets the package as a 'drop-in replacement for @solana/web3.js'. Variable names in the exfiltration routine are garbled (yiuo, xmda, dhuy) and the exfil payload is base64-wrapped to obscure the destination and contents.

Malicious versions

1 flagged

2.1.0

Indicators of compromise (SHA-256)

54d27d76902370899c3362602581cdec59396e1ece2bd87976f1798083957f89

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 @wethenorth12/solana-web3 (version 2.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/solana-web3 across your stack and pipelines.
If you installed it — respond
@wethenorth12/solana-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 @wethenorth12/solana-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 @wethenorth12/solana-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. @wethenorth12/solana-web3 on npm has been identified as a malicious package (version 2.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013454

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/solana-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database