Private keys or other sensitive input passed for decoding are disclosed to the bot recipient.
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 package’s exported decoder sends its input, labeled as a private key, to a Telegram bot before returning the expected decoded value. This is a concrete credential-exfiltration path triggered by the package’s normal API.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer calls the exported decode function.
Mechanism
The function sends the input, labeled “private key=”, to an obfuscated chat identifier using a hard-coded bot token, then performs the expected decode.
Attack narrative
When a consumer calls decode, the package sends the supplied value to a Telegram chat using a hard-coded bot token, labeling it as a private key. The function then returns the normal Base58-decoded result, concealing the credential theft within the expected operation.
Avoid installing node-bs58.js@3.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.