Binance Revokes SignalPlus API Keys After Security Alert, Urges Users to Review Accounts

Binance shuts off SignalPlus access

Binance has cut off SignalPlus’s access to every connected account after the trading platform reported a possible security issue. The exchange said it revoked the API keys on Thursday, Nov. 5, as a precaution, and emphasized that its own systems were unaffected and user funds remained safe.

API keys allow services such as SignalPlus to access account information and place trades without a user signing in to Binance. With the keys revoked, SignalPlus cannot interact with those accounts unless users generate and connect new keys.

The move puts the immediate disruption on users who relied on SignalPlus to view accounts or manage trades through Binance. Revoking a key cuts off that connection, but it doesn’t tell users whether anything happened before the revocation. That distinction matters: access has been stopped, while the available information about the reported issue remains limited.

Binance framed its action as a precaution and said its own systems weren’t affected. That assurance addresses the exchange’s infrastructure, but it doesn’t explain what SignalPlus detected, what access might have been involved, or whether any connected accounts experienced suspicious activity. Those are separate questions, and the exchange hasn’t answered them in the information available so far.

Get Unchained’s crypto news in your inbox with the free Unchained Daily newsletter.

Steps for SignalPlus users

Binance told affected users to sign in to the exchange directly and inspect their positions and open orders. It advised them to wait for SignalPlus to confirm the issue is resolved before creating or reconnecting API keys. The exchange also recommended IP whitelisting, which restricts a key’s use to specified internet addresses.

That sequence is practical. A direct sign-in gives users a way to check their account without relying on the third-party connection that Binance has disabled. Reviewing open orders and positions can also help users understand what remains active on the exchange, even though the guidance doesn’t establish whether SignalPlus changed anything before access was cut off.

Waiting for SignalPlus to confirm resolution before reconnecting is a cautious step, because a new key would restore access to the account. Users who do reconnect can limit where a key works by allowing only specified internet addresses. The restriction can reduce exposure if a key is used somewhere unexpected, though it doesn’t answer what caused the reported issue.

Binance urged other third-party services connected to the exchange to review their security controls, monitor for suspicious activity and promptly report concerns to Binance.

That request broadens the incident beyond the accounts already disconnected. It signals that Binance wants other services and their customers to check their own access arrangements, even though the exchange hasn’t said that another service is involved. For users, a connected service is a useful convenience with a real trade-off: it receives a form of access to an exchange account, and that access needs active oversight.

Details remain unclear

Binance did not identify the security problem or say how many accounts were connected to SignalPlus. Its post also did not report whether users had lost funds. As of publication, SignalPlus had not issued a statement in the sources reviewed by Unchained.

The gaps limit what readers can conclude. “Possible security issue” describes a concern, not its cause or scope, and the lack of a reported loss doesn’t establish that every account was untouched. Until more detail is available, users have little basis for judging whether the risk was tied to a particular account, a key, or SignalPlus’s broader service.

Binance co-founder Changpeng Zhao advised SignalPlus customers to revoke their API keys on other exchanges as well. “If you use SignalPlus for any other exchange platform, it’s time to revoke all your API keys,” Zhao wrote on X. He added that users generally should not store API keys with third-party platforms.

Zhao’s advice extends the precaution beyond Binance, where the exchange has confirmed it disabled SignalPlus keys. That’s a meaningful distinction: his warning is a recommendation to customers, while the reported action by Binance is a specific response to the issue. Users who follow the advice would need to check each exchange account where they’ve connected SignalPlus and consider what access remains active.

Zhao also said derivatives exchange Deribit had reported the issue, writing, “Deribit also/first reported this.” A Crypto Times headline said Deribit had revoked SignalPlus keys too; Unchained has not independently verified that report.

That attribution offers a clue about how the concern reached Binance, but it doesn’t fill in the missing technical details. The report about Deribit’s response remains unverified by Unchained, so it shouldn’t be treated as confirmation of what happened there. Here’s the thing: when several platforms are mentioned, the exact status at each one matters to users deciding which accounts to check.

Why API access matters

Revoking a key limits what a connected service can do, but users still need to check the activity already associated with their accounts. Binance’s guidance focuses on reviewing positions and open orders, then using IP restrictions if and when users reconnect a third-party service.

An API key is a permission mechanism. Depending on the access granted, a connected service can retrieve account information or place trades without the user signing in through the exchange each time. That makes the setup convenient for trading tools, but it also means users should understand what permissions they’ve granted and which services still hold working keys.

In this case, Binance says the keys connected to SignalPlus have been revoked. That stops the service from using those keys to interact with the affected Binance accounts, but it doesn’t remove the need to inspect account activity. Users should also be careful not to treat a new key as a routine reset: reconnecting restores a channel of access, so it makes sense only after the user is satisfied the issue has been addressed.

This is more significant than it looks. The immediate action is simple, but it puts responsibility on users to verify their own positions and decide whether to restore a third-party connection. If you’re working in this space, the episode is a reminder that integrations add another point to monitor whenever account access depends on credentials held outside the exchange (and this is the part most people overlook).

Access revoked. Questions remain.

What happens next for connected users

The next useful information would be a clearer account from SignalPlus about the possible security issue and whether it has been resolved. Binance’s notice gives users a concrete step to take now, but its limited detail leaves them unable to assess the incident’s scope from the notice alone. Until there’s more information, the exchange’s advice to check accounts and hold off on reconnecting is a measured response.

For customers, the practical choice is whether the convenience of a connected trading service warrants restoring access after the provider says the issue is fixed. IP whitelisting can narrow where a key may be used, but users still need to review permissions and monitor activity. The durable lesson is straightforward: third-party access can be useful, yet it makes account security a shared responsibility between the exchange, the service and the customer.

Related Listen: Binance Lost $6.3 Billion in 20 Minutes. Can Crypto Stop the Next One?

The post Binance Pulls Every SignalPlus API Key, Tells Users to Check Their Positions and Orders appeared first on Unchained.