SignalPlus API Keys Revoked by Binance After Security Alert

Binance revoked SignalPlus API keys on November 5 after the trading infrastructure provider reported a potential security issue. Binance called the move precautionary, said its own systems were unaffected and customer funds remained safe. The vulnerability’s cause and scope are still unknown.

What happened to SignalPlus API keys

Decrypt reported on November 5, citing Binance’s announcement, that the exchange revoked every API key associated with SignalPlus after the platform identified a potential security vulnerability. Binance said the step was a precaution and its internal systems and user funds were unaffected.

U.Today reported that Binance posted the notice on its official Square feed. The exchange said revoking the keys would prevent possible unauthorized access through connections between Binance accounts and SignalPlus. It told users to log in to Binance directly to review open positions and orders, and to wait for SignalPlus to confirm the issue is resolved before reconnecting. Binance also recommended IP whitelisting for API keys.

The available reports don’t identify the flaw, say when it was discovered or establish whether anyone accessed accounts or lost funds. Binance’s action ends the existing connection, but doesn’t show whether credentials were exposed or what safeguards SignalPlus is applying.

Binance also asked other third-party platforms connected to its exchange to review security controls, monitor unusual activity and report concerns. That request addresses integration risks, not evidence that Binance itself was breached in this incident.

Background: why SignalPlus API keys matter

SignalPlus provides trading infrastructure and analytics for cryptocurrency derivatives. Traders can manage positions and run strategies across exchanges through API connections, according to U.Today. An API key lets software interact with an account and platform features. Binance’s API-key terms describe this programmatic access, so removing SignalPlus-linked credentials cuts off that integration without requiring users to move assets to the service.

The permissions assigned to an API key can limit what connected software can do. If credentials are compromised, an attacker could potentially use those permissions for unauthorized activity, including trading. The reports don’t establish that this happened to SignalPlus users. The incident highlights how API keys connect third-party tools with exchange accounts.

The news came shortly after a separate Binance security incident. In a November 3 update, Binance said an October 29 incident affected about $6.34 billion in digital assets, with about $2.85 billion frozen or intercepted, subject to reconciliation and market-price changes. The exchange said it had set aside more than 100% of the funds needed to cover the loss. As of October 31, it had replenished 98% of impacted token assets and was still buying less-liquid assets.

Binance said the investigation was ongoing and would receive independent review. Its update said the latest information from the FBI indicated North Korea was responsible. The November 3 incident update concerns that earlier event, not the SignalPlus vulnerability.

These are separate reported incidents. The available evidence does not connect the October 29 incident to the SignalPlus vulnerability.

Market data on November 5

Nothing in the available reporting links the SignalPlus action to token prices. At 13:17 UTC on November 5, CoinGecko data showed Bitcoin, Ethereum and BNB higher over 24 hours, though each had declined in the prior hour. This is a market snapshot, not proof of cause or a direct measure of sentiment toward Binance.

Alternative.me’s Crypto Fear & Greed Index was 50, or Neutral, on November 5. The available market and sentiment data don’t isolate the announcement’s effect.

What to watch next for SignalPlus API keys

A useful update would explain the vulnerability, whether credentials or accounts were exposed, and what SignalPlus has done to resolve it. Neither company had provided those details in the reports available on November 5. Readers should distinguish confirmed findings from speculation about cause or impact.

Binance’s instructions are to inspect positions and orders by accessing Binance directly, wait for SignalPlus to confirm resolution before reconnecting, and use IP whitelisting for API keys. Crypto.news reported that Binance co-founder Changpeng Zhao advised traders who used SignalPlus with other exchanges to revoke those keys and warned against storing exchange credentials with outside service providers. This is advice, not confirmation that other exchanges were affected.

Watch for a clear SignalPlus security update and revised Binance guidance before the integration resumes. U.Today noted the measure could potentially disrupt automated trading strategies that rely on the connection.

FAQ

Why did Binance revoke SignalPlus API keys?

Binance removed the keys after SignalPlus reported a potential security vulnerability. The exchange said it acted as a precaution against possible unauthorized access through the integration.

Are SignalPlus API keys safe to use again?

The reports don’t confirm that the vulnerability has been fixed or disclose its technical details. Binance told users to wait for SignalPlus to confirm resolution before reconnecting.

Were Binance customer funds affected by the SignalPlus issue?

Binance said its systems were unaffected and user funds remained safe. The reports don’t confirm account access or financial losses tied to the SignalPlus issue.

Sources

• 29 October 2026 Binance Security Incident: Initial Findings and Response Update (www.binance.bh)
• Binance Cuts Off SignalPlus API Keys Over 'Potential Security Issue' at Trading Platform (Decrypt)
• Binance Revokes API Keys, Security Issue Found at SignalPlus (U.Today)

This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrencies are highly volatile; always do your own research before investing.