What exchanges confirmed

Binance said it proactively removed every API key linked to SignalPlus after the third-party trading platform reported a potential security issue. Binance said its own systems were unaffected and directed users to review positions and open orders from the exchange’s official interface.

Reuters reported that Deribit took the same precaution and said its investigation found no indication that Deribit systems or data were compromised. Coincall separately advised current and former SignalPlus users to revoke related keys, check recent activity and avoid reconnecting until further notice.

What SignalPlus says happened

SignalPlus said the attack began with a compromised Telegram account belonging to a contact at a technology vendor. According to the company’s statement, an attacker used that identity to send a fake Microsoft Teams invitation to an engineer, compromising the engineer’s computer before attempting to move through SignalPlus’s internal network.

The company said it contained the intrusion, suspended platform services and coordinated with exchanges to disable linked keys. It put total losses below $82,000 and promised full reimbursement. Those figures and the described attack path are SignalPlus’s claims; a complete independent forensic report has not been published.

Why a non-withdrawal API key still matters

Trading permissions can be damaging even when a key cannot withdraw funds. An attacker may be able to place or cancel orders, alter derivatives positions, create losses through thin markets or disrupt automated risk controls. Revoking a key stops future use, but it does not undo orders or positions created before revocation.

IP allowlisting narrows where a key can be used. SignalPlus acknowledged, according to its disclosure, that it had not previously made that control mandatory for exchange API access. Allowlisting is useful defence in depth, not proof that an integration is safe.

What SignalPlus users should do now

  1. Log in through each exchange’s saved bookmark or official app—not through a message or “security check” link.
  2. Confirm the SignalPlus key is disabled or delete it manually on every connected venue.
  3. Review open orders, positions, fills and recent account activity for anything you do not recognise.
  4. Contact the exchange through its official support channel if an unauthorised trade appears.
  5. Do not reconnect SignalPlus until both the platform and the relevant exchange confirm that service can resume.
  6. When creating future keys, grant only necessary permissions and use IP allowlisting where supported.
Removing a key closes the connection. It does not prove that nothing happened while the connection was active.

What remains unknown

SignalPlus has not published a complete forensic timeline, a full account-impact count or an independent audit. It is also not yet clear whether every exchange connected to the platform has completed its own review. Users should treat reimbursement and restoration timelines as company commitments until completed.

EVIDENCE LEDGER

Sources you can open

01
Binance — SignalPlus key revocationExchange confirmation and direct user instructions.
OPEN ↗
02
Coincall security advisoryPrecautionary guidance for current and historical SignalPlus connections.
OPEN ↗
03
Reuters — Binance and Deribit responseIndependent corroboration of the exchange actions.
OPEN ↗
04
CoinDesk — account implicationsIndependent reporting on the API-key risk and user guidance.
OPEN ↗
Phishing warning

This article does not link to an account-fix form. Open exchanges from a saved bookmark or official app. No legitimate support agent needs your seed phrase, private key or authenticator code.