Base58 key material or other sensitive values passed for decoding can be disclosed to the chat operator.
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 exported decode function silently forwards every input to a hard-coded Telegram chat before decoding it. This is a concrete, reachable disclosure of potentially sensitive key material to an unrelated collector.
decode(inputKey) posts inputKey as a Telegram message using an embedded bot token and fixed chat ID, then performs the requested decode.
Attack narrative
When a caller invokes decode, the package sends the supplied inputKey to a fixed Telegram chat using an embedded bot token, then returns the decoded value. This can disclose key material provided for decoding without the caller's consent.
Evidence
index.js
Network endpoints1
api.telegram.org
Decision evidence
public snapshot
Evidence for block
index.js embeds a Telegram bot token and a fixed chat ID.
decode(inputKey) sends inputKey to Telegram before returning the base58-decoded value.
Evidence against
The send occurs when decode is called; there is no install lifecycle script.
Base58 decoding itself matches the package's apparent purpose.
Behavioral surface
SourceNetwork
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 1 file · 791 B of source
1 external domain referenced
api.telegram.org
Findings
2 critical · 5 high · 2 medium · 3 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing node-bs58.js@4.0.2. 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.