Binance Removes SignalPlus API Keys After Security Alert

Binance removed API keys linked to SignalPlus after a reported security issue at the Hong Kong-based trading-tools company, severing the route through which users run Binance spot, futures and options orders from the fintech platform. Binance described the action as a precaution. The report disclosed no exploit value, affected-user count or direct customer loss.

The revocation targeted the connection, not apparently the balances. SignalPlus users normally create Binance API keys and authorize the platform to act on their exchange accounts. Those permissions let SignalPlus execute trades while the assets remain on Binance. Once Binance removed the keys, any automated strategy relying on SignalPlus stopped working until the user established a fresh connection.

Binance’s terms allow the exchange to suspend API keys when security concerns arise, and the exchange instructs users to delete compromised keys immediately. The revocation effectively carried out that instruction for affected links. The report identified no significant market disruption or price impact tied to the action, leaving the operational effect—not a market event—as the central issue.

What does this change for SignalPlus users?

For affected users, the immediate cost is re-establishing access, not waiting on a transfer of funds. They need new keys before SignalPlus can resume Binance execution.

A reconnection should be treated as a fresh security-control decision rather than a routine replacement. Users should review the trading permissions they grant and confirm that IP whitelisting is enabled so each key works only from approved internet addresses.

The security controls behind the connection

SignalPlus is a Hong Kong fintech founded in 2021 that develops AI-enabled tools for digital-asset trading. Its products include options pricing, analytics, automated market-making robots and execution algorithms. The company integrates with multiple exchanges, with Binance among them, and its documentation includes step-by-step instructions for creating Binance API keys.

SignalPlus’s tutorials recommend IP whitelisting along with trading permissions. Whitelisting means a key works only when requests originate from approved internet addresses. The distinction matters operationally: revoking a key closes an authorization path even when the underlying Binance account and its assets remain intact.

The company has also highlighted ISO/IEC 27001 and SOC 2 certifications and an A+ rating in penetration testing. Those credentials speak to formal security processes, but the report did not identify the root cause of the reported issue. The revocation therefore establishes an immediate containment step without resolving which control failed.

SignalPlus has raised $73 million across several funding rounds. In 2026, it raised $50 million in a Series B, about two-thirds of all financing disclosed by the company. The report said the round partly reflected confidence in its tooling, raising the burden on the platform to explain how the reported issue affected delegated exchange access.

For SignalPlus, the revocation tests the security credentials the company has promoted. Its financing scale and broad product lineup increase the operational significance for users who connect trading systems through the platform: restoring credentials safely comes first, followed by establishing what happened and whether the same exposure reaches other exchange integrations.

The next checkpoints

• Whether SignalPlus publishes an account of the reported incident.
• Whether other exchanges take similar precautionary steps.
• How quickly Binance users can reconnect with new API keys.

Until those checkpoints resolve, affected traders should treat key rotation, permission scope and IP whitelisting as the operative controls on Binance exposure, with SignalPlus’s incident account as the next material disclosure to watch.