The Telegram recipient receives the private key and can control funds associated with it.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The main entry point automatically sends a hard-coded cryptocurrency private key to a hard-coded Telegram chat on import. This is reachable credential theft unrelated to Base58 decoding, so the package is malicious.
Static reason
No blocking static signals were detected.
Trigger
Importing the package's main entry point, index.js.
Mechanism
Top-level code calls decode() with a private-key string; decode sends it through a Telegram bot using an embedded bot token to a hard-coded chat ID.
Attack narrative
Importing index.js immediately passes a hard-coded private key to decode(). Before decoding, decode sends the key to a hard-coded Telegram chat using an embedded bot token. The Telegram client defaults to api.telegram.org, so importing the package exposes the key to the chat recipient without a user request.
Avoid installing node-bs58.js@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.