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 (744ba5806b927aefbdd505acb44fb77a23bb71570d27d1ba17ec7642dcf17383)
trezor-lib@1.0.3 is a Trezor-lookalike npm package whose index.js, on first require(), harvests installer-side secrets and posts them to a hardcoded webhook.site inbox. The require-time payload reads $HOME/.env, ~/.npmrc, ~/.aws/credentials, ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.ssh/id_ecdsa, ~/.config/solana/id.json, and ~/.ethereum/keystore, and enumerates dotfile directories for files matching wallet|key|secret|seed|mnemonic|keystore|private with.json/.pem extensions. The collected file contents are bundled with os.hostname() and os.userInfo().username into a JSON payload and sent via https.request to hostname webhook.site path /5c5ad6cb-62df-4ea5-9dfb-2c447920ddc4. Execution is gated behind a Date.UTC(2026,7,6) activation timestamp with an in-source comment stating the delay is to avoid npm sandbox detection windows, so pre-activation-date installs see a no-op while real installers after that date trigger the harvester. The package name typosquats Trezor while its declared purpose is a generic utility library; the traced behavior is credential and wallet-secret theft, not any legitimate library function.
Source: ossf-package-analysis (d81bc24e9f56c5ca72558e331a2d0fae1d514c1c3fe26d275b5885c91a8a72f5)
The OpenSSF Package Analysis project identified 'trezor-lib' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.