Binance removes SignalPlus API keys: check positions and open orders

The immediate question is what remains in the account

The reported action concerns API keys used by a third-party service. For an affected reader, the first practical question is whether the positions and orders shown directly in Binance match the trading activity they intended. Key removal is a security action. The report does not say that removing a key also closes every position or cancels every outstanding order.

Treat those as separate checks. Review the current positions, then review orders that are still open. Compare them with the last activity you meant SignalPlus to carry out. If something is unfamiliar, preserve the relevant record before making additional changes so that you can identify the activity when contacting the platform's support.

This distinction avoids a costly inference: an interrupted connection does not, on the evidence in this report, demonstrate that the trading account has no remaining exposure. The reader task is to establish the account's actual state from its own screens. It is not to assume a position outcome from a headline about access credentials.

What Binance said, and what the report does not answer

Odaily attributes the removal to a potential security issue reported by SignalPlus. It describes Binance's action as precautionary and reports the exchange's statement that its systems were unaffected and customer funds remained safe. Preserve that attribution when discussing the event.

The readable report does not provide a confirmed loss total, a count of affected customers, a technical root cause or a timetable for restoring the connection. We have not established those details from another readable source in this run. No amount or customer count should be inferred from the decision to remove keys.

There is also a difference between the exchange's description of its systems and a reader's own order history. The exchange statement does not replace checking an individual account. Conversely, discovering an unfamiliar order would require investigation; this report alone would not prove who placed it or which system caused it.

The event therefore supports a narrow conclusion: Binance reported taking a protective access action in response to a third-party concern. It supports specific account checks. It does not support calling the matter a confirmed new theft or assigning a loss figure.

Reconnection needs a stated resolution

The instruction relayed by Odaily is to reconnect only after SignalPlus confirms the issue is fully resolved. Read that condition literally. The presence of a reconnect button or a request to create a replacement key is not the confirmation described in the report.

Before restoring the integration, look for a clear statement from SignalPlus addressing the problem and the conditions for using the service again. Retain the source and its time. If the statement does not answer whether the issue is resolved, the reported condition has not been established by that statement.

Binance's advice also includes using an IP whitelist. Follow the exchange's documented settings for the integration you are using. This article does not supply IP addresses, permission settings or a replacement credential procedure because none is specified in the event report. Copying such values from a public discussion would introduce a new instruction unsupported by this source.

The same separation applies to support messages. A report about removed keys does not authorize a stranger to request a new key, a secret or a verification code. Use the platform's own support path when you need help identifying an account record. Keep credentials out of the conversation.

What to check now on Binance

• Open Binance directly and inspect the positions associated with your trading activity. Compare the displayed instruments and direction with what you intended to hold.
• Check open orders separately. Identify any order that you do not recognise and retain its details before deciding how to handle it.
• Check the integration status against the reported key removal. Do not interpret a disconnected third-party screen as proof that positions have closed.
• Read SignalPlus's own resolution statement before considering reconnection, then apply the exchange's IP whitelist guidance through its documented account settings.

Use the order identifiers and position records to keep each check attached to the right account activity.

If an existing position needs monitoring, the funding-rates board can provide broader market context. It cannot show the complete state of your private Binance account. Read your account's own position and order records for decisions about that account.

Keep the event separate from market signals

A trader following security news may also watch funding or price movements. Neither the opened event report nor the fact of API removal establishes a market-wide reaction. We are not attaching a price change, liquidation total or directional trading recommendation to this story without corresponding observations.

If you use the funding-rates board alongside the account review, compare the instrument and observation time with the position you actually hold. Market context and account access solve different questions. A funding observation does not confirm that an integration is secure, and a security statement does not settle the cost of an open position.

The report also says Binance urged third-party providers connected to its platform to review security measures, monitor unusual activity and contact Binance when issues are found. That provider-level request is separate from the customer action: inspect the account and wait for the stated resolution before reconnecting.

Build an account record before restoring automation

A useful account review has a sequence. First establish what the exchange currently shows. Then compare that state with the last instruction you intended the connected service to execute. Finally, identify what remains unresolved before considering reconnection. This is a way to organise the account checks in Binance's reported advice, rather than a claim about how the security issue occurred.

Keep a position and an order as separate entries when recording that review. A position describes exposure already shown in the account; an open order is something you must examine in the order list. The event report does not say that either list was automatically cleared. If you treat them as one item, you may overlook the very record you need to ask support about.

For an unfamiliar entry, preserve its identifier, instrument and the time displayed by the account. Write down which intended action you are comparing it with. This gives a support request a specific subject. A message saying only that the third-party connection stopped leaves unanswered which account activity needs investigation.

Reconnection is a later decision in this sequence. Compare the provider's resolution statement with the question you actually need answered: whether the reported issue has been fully resolved and what conditions apply to using the connection again. Do not use a general message about normal service as a substitute for reading what it says about this particular problem.

If the available statement leaves that question open, preserve the statement alongside your account records and seek clarification through the platform's own support channel. Keep the unresolved point precise. The evidence may establish that keys were removed while leaving the root cause or restoration conditions unanswered; each question should retain its own status.

Quick answers

Did the report confirm a new loss of customer funds?

No loss amount is supplied in the readable Odaily report. It reports Binance's statement that user funds remained safe. That statement is attributed to Binance rather than presented here as an independent account audit.

Does removing a key cancel my open orders?

The report does not establish that result. Inspect the open-order list and positions directly instead of assuming that access removal changed their state.

Can I reconnect as soon as the interface permits it?

The advice reported by Odaily uses a different condition: SignalPlus must confirm the problem is fully resolved. An available button does not itself answer that condition.

What information is still missing?

The opened event source gives no confirmed loss total, affected-user count, technical root cause or restoration deadline. Watch for a specific resolution statement and compare it with the current account records before restoring the connection.