• Binance stated its internal systems were unaffected and customer funds remain safe.

• Binance urged SignalPlus users to review open positions and open orders directly on the exchange.

• The exchange recommended IP whitelisting and no key rebinding until SignalPlus confirms resolution.

Binance Pulls All SignalPlus Keys

Binance has revoked all API keys associated with SignalPlus after the third-party trading infrastructure provider reported a potential security vulnerability on its side. In an official statement posted on X on Thursday, November 5, the exchange described the removal as an immediate precautionary measure taken to protect users, adding that its own systems were unaffected and that customer funds remain safe.

The announcement sets out the practical consequences for affected customers. Anyone who used SignalPlus is asked to log into their Binance account directly, check open positions and open orders, and hold off on rebinding any API keys until SignalPlus confirms full resolution. Binance also recommends enabling IP whitelisting, a setting that lets a key operate only from pre-approved addresses and limits the damage if credentials leak. The statement extends beyond individual users: third-party platforms integrated with the exchange are encouraged to review their security controls, monitor for unusual activity and report any concern without delay.

Considerable detail is still missing. The precise nature of the security issue has not been explained, the number of users affected is unknown, and no attacker access to customer accounts or resulting financial losses has been confirmed. Binance's wording treats the case as a potential exposure rather than a verified breach. Its standing security guidance tells users to revoke potentially compromised credentials at once and restrict API permissions to the minimum functions needed, a playbook Thursday's action follows to the letter. For SignalPlus users, restoring automated functionality will require generating new credentials once the integration is judged secure.

SignalPlus and the API Permission Chain

SignalPlus supplies trading infrastructure and analytical tools for cryptocurrency derivatives markets, giving traders one interface to manage positions and run strategies across multiple exchanges through API integrations. The platform covers options analytics, risk management and automated execution, which is why its user base overlaps heavily with active contract trading desks. These connections let external applications act on exchange accounts without customers ever moving assets off the platform.

That convenience depends on permissions. An API key can be scoped to read account data, place trades across different order types, or manage positions; depending on what the user grants, a leaked or misused key can expose an account to unauthorized trading activity. The distinction matters: unlike a private key, which ultimately controls the funds themselves, an API key grants limited and revocable access, but within its scope it can still alter positions without the owner's consent.

The revocation therefore cuts both ways for SignalPlus users. Unauthorized-access risk through the integration drops on the Binance side, yet every automated strategy that relied on the connection, including AI trading bot setups and systematic options hedging, has stopped managing those accounts. Open positions remain on the exchange but no longer respond to the third-party application's logic, so a hedged book can drift from its intended state until the trader intervenes manually. API-related incidents at third-party tools are not new either: in 2022, the exposure of credentials tied to trading platform 3Commas triggered security warnings and waves of key revocations across several exchanges.

Precaution, Not a Confirmed Breach

The primary record here is Binance's own announcement, and it is careful: the exchange claims no confirmed compromise, no confirmed loss and no confirmed account access, only a potential issue reported by SignalPlus. Reading the move as a proven attack would go beyond what that document states. The practical takeaway is operational rather than forensic. Funds were never at direct custody risk under this setup, but active automated strategies face an interruption whose length depends entirely on when, and whether, SignalPlus publishes technical findings. Traders with open derivative positions routed through the platform should treat manual review as the default until the integration is cleared, and anyone rebinding keys should enable IP whitelisting before reconnecting.