If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (94f602036ff9f524298056528fbec6c58c9fb66ea2686bec418694b5854aeea4)
On require(), index.js collects the full process.env object together with hostname, username, home directory, platform, current working directory, and a timestamp, JSON-encodes and base64-encodes the payload, and issues an HTTPS GET to api.telegram.org/bot<token>/sendMessage with a hardcoded bot token and chat_id. A tmp-file flag suppresses re-sending. The package advertises itself as a 'Drop-in replacement for bitcoinjs-lib' under an unrelated scope and ships only stub wallet functions alongside this exfiltration payload, consistent with a typosquat lure targeting bitcoinjs-lib users. In modern development and CI environments, process.env routinely contains cloud credentials, npm/GitHub tokens, and database passwords, all of which are sent to the attacker-controlled Telegram chat on module load.