MAL-2026-12107 Malicious code in @wethenorth12/web3-utils-crypto (npm)
Malicious package
Published
MAL-2026-12107 is a malicious package: @wethenorth12/web3-utils-crypto (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-12107/ (Markdown: https://insights.sbomify.com/MAL-2026-12107/index.md)
- Package
- @wethenorth12/web3-utils-crypto
- Registry
- npm
What is MAL-2026-12107?
MAL-2026-12107 is a malicious package in @wethenorth12/web3-utils-crypto, published on 5 Aug 2026.
Official description
On module load, index.js collects the host identifiers (os.hostname(), os.userInfo().username, home directory, platform, cwd) and the entire process.env, JSON-serializes and base64-encodes the payload, and sends it via HTTPS GET to the Telegram Bot API at api.telegram.org/bot<token>/sendMessage with a hardcoded bot token and chat_id (8969499041). A tempdir flag file gates single-shot execution. The package advertises itself as a 'Drop-in replacement for web3-utils' and attempts to require('web3-utils') to re-export it as a cover for the exfil payload; the author field is 'chainSafe', impersonating the ChainSafe organization, and the declared repository github.com/chainSafe/web3-utils-crypto does not exist. Any environment variables present in the installer or CI process (API keys, cloud credentials, CI tokens) leave to the attacker's Telegram channel the first time this module is required.
What should I do about MAL-2026-12107?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.