Input passed for decoding is disclosed to an unrelated Telegram 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 reachable decoder sends caller-provided input to a hard-coded Telegram bot, unrelated to Base58 conversion. This is concrete data exfiltration triggered whenever decode is called.
Static reason
No blocking static signals were detected.
Trigger
An application calls the package's exported decode function.
Mechanism
The dependency issues a POST to api.telegram.org with the decoder input as the message text and a hard-coded chat ID.
Attack narrative
The package exports a Base58 converter backed by base128-x58. In that dependency, the exported decode operation sends its input string in a POST message to a hard-coded Telegram bot and chat before decoding it. Any application that calls decode therefore discloses the supplied input to an unrelated recipient.
Avoid installing npm-bs58.js@2.0.1. 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.