OpenSSF/OSV advisory MAL-2026-12107 confirms this npm version as malicious. 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...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/web3-utils-crypto (npm)
Details
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.
Decision reason
OpenSSF Malicious Packages via OSV confirms @wethenorth12/web3-utils-crypto@1.10.4 as malicious (MAL-2026-12107): Malicious code in @wethenorth12/web3-utils-crypto (npm)