binance-account

SUSPICIOUS. The skill’s read-only Binance monitoring purpose is broadly coherent, and the Binance documentation links are official. However, authenticated account data and secrets are routed through a non-Binance internal proxy, and the skill relies on an unofficial third-party library without pinning or integrity guidance. These trust and data-flow choices are disproportionate enough to raise concern, though there is no evidence of overt malware or download-execute behavior.

The code is primarily a Binance account-reporting tool and contains no clear malware, destructive behavior, or deliberate credential exfiltration logic. The main risks are the hardcoded proxy credential, routing sensitive authenticated traffic through an internal proxy, and exposing detailed financial records on stdout. The read-only safety claim is not enforced by the code; API-key permissions must be independently verified. The futures_account_transfer invocation appears erroneous but is unlikely to execute a transfer because required parameters are missing.

The code is primarily a Binance account-reporting utility and does not show clear malicious functionality. It performs sensitive read operations and prints financial data, consistent with its stated purpose. The hardcoded proxy username/password and forced routing of authenticated traffic through an internal proxy are significant security concerns; the proxy credential should be moved to protected configuration and the proxy's trustworthiness and TLS behavior should be verified. The code also relies on API keys being read-only without enforcing that restriction.