MAL-2026-12102 Malicious code in @wethenorth12/solana-web3 (npm)
Malicious package
Published
MAL-2026-12102 is a malicious package: @wethenorth12/solana-web3 (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12102/ (Markdown: https://insights.sbomify.com/MAL-2026-12102/index.md)
- Package
- @wethenorth12/solana-web3
- Registry
- npm
What is MAL-2026-12102?
MAL-2026-12102 is a malicious package in @wethenorth12/solana-web3, published on 5 Aug 2026.
Official description
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.
What should I do about MAL-2026-12102?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.