SKN | Binance Revokes SignalPlus API Access After Security Warning, Urges Traders to Review Accounts

Key Points:

• Binance removed all API keys linked to SignalPlus after the third-party trading platform reported a potential security issue, describing the action as a precautionary measure.
• The exchange said its own systems were unaffected and customer funds remained safe, while advising users to review open positions and orders directly through Binance.
• Deribit also removed SignalPlus-linked API keys, highlighting the broader security risks associated with third-party trading integrations and exchange account permissions.

Binance has severed trading connections with third-party platform SignalPlus following a reported security concern, reinforcing the importance of cybersecurity across cryptocurrency trading infrastructure. The exchange said its internal systems were unaffected and customer funds remained safe, but the decision comes at a particularly sensitive time for the industry following a major security incident involving Binance in late October.

Binance Disables SignalPlus Connections as a Precaution

On November 5, Binance announced that it had proactively removed all API keys associated with SignalPlus after the platform reported a potential security issue. The measure immediately interrupted the connections that allowed SignalPlus to interact with Binance accounts.

The exchange emphasized that the latest development did not indicate a compromise of its own infrastructure. It also stated that user funds remained safe. However, the precise nature of the SignalPlus security concern, the number of potentially affected customers, and whether unauthorized parties accessed account information or trading permissions have not been publicly established.

Binance instructed affected customers to log in directly to their exchange accounts and review their open positions and outstanding orders. It also recommended waiting until SignalPlus confirms that the issue has been fully resolved before establishing new API connections.

The response demonstrates how exchanges can restrict external access without necessarily suspending their broader trading operations. For active traders relying on automated execution, however, the removal of API credentials can interrupt established strategies and require manual account management.

API Permissions Highlight Third-Party Trading Risks

API keys allow external applications to communicate with cryptocurrency exchanges and perform authorized functions on behalf of account holders. Depending on the permissions granted, these connections may provide access to account information, order placement, and automated trading activity.

This functionality is particularly relevant to derivatives traders who use specialized platforms to manage strategies across multiple exchanges. However, it also creates an additional security dependency: protecting an exchange account requires attention not only to the exchange itself but also to every external service holding authorized credentials.

Binance recommended enabling IP whitelisting when establishing future API connections. This security measure restricts API access to approved internet addresses, reducing the possibility that exposed credentials can be used from unauthorized locations.

The exchange also encouraged other third-party platforms integrated with Binance to review their security controls, monitor unusual activity, and report potential concerns immediately. Binance co-founder Yi He reinforced the message, describing the responsibility as an industry-wide issue rather than a concern limited to one provider.

Importantly, derivatives exchange Deribit also removed SignalPlus-linked API keys. Reuters reported that Deribit found no evidence that its own systems or data had been compromised. The parallel precautionary response illustrates how a security concern involving one service can prompt action across multiple trading venues.

Recent Binance Security Incident Raises the Stakes

The SignalPlus decision follows a separate Binance security incident reported on October 29, which involved approximately $6.34 billion in affected digital assets. Binance subsequently disclosed that approximately $2.85 billion had been frozen or intercepted, while stating that 98% of impacted token assets had been replenished as of October 31.

These figures relate to the earlier incident and should not be interpreted as evidence of losses connected to SignalPlus. Nevertheless, the timing has intensified attention on exchange security, credential management, and the operational risks surrounding external integrations.

The broader implication is that institutional and professional trading operations increasingly depend on interconnected systems. A weakness at a service provider can create operational exposure even when the underlying exchange reports that its own infrastructure remains unaffected.

What Traders and Institutions Should Monitor

The immediate priority is confirmation from SignalPlus that the reported security issue has been resolved. Until then, Binance’s recommendation is to avoid reconnecting API credentials and to manage positions directly through the exchange. Investors and trading firms will also be watching for further disclosures concerning the incident’s scope, affected integrations, and any evidence of unauthorized activity.

For the wider crypto market, the episode reinforces the need for stronger third-party risk management, restricted API permissions, and continuous monitoring of automated trading connections. As institutional participation expands, confidence in digital asset markets will depend not only on exchange security but also on the reliability of the broader technology ecosystem supporting execution and custody.