SignalPlus Incident Highlights How Crypto Trading API Keys Can Put Funds at Risk

Daily Feed
SignalPlus Incident Highlights How Crypto Trading API Keys Can Put Funds at Risk

Your Crypto Trading Bot Can Lose Money Without Withdrawal Access

Trading permissions alone can expose an exchange account to losses. In the SignalPlus incident, though, the permissions assigned to the affected API keys have not been made public. It remains unclear whether they could withdraw funds or only trade.

  • Binance and Deribit revoked API keys linked to SignalPlus.
  • Both exchanges said their own systems were unaffected.
  • SignalPlus blamed the intrusion on a compromised vendor contact and a fake Teams invitation.
  • Customers were told to check orders and positions directly with their exchanges.

What SignalPlus said happened

SignalPlus said it detected unusual activity in the early hours of Nov. 4, 2026. The company said an attacker used a technology vendor contact’s compromised Telegram account to send a SignalPlus engineer a fake Microsoft Teams invitation. According to SignalPlus, the engineer’s computer was compromised, giving the attacker access to the company’s internal network through the employee’s account.

Public forensic findings have not independently confirmed that account of the intrusion. SignalPlus said it blocked the activity, closed identified vulnerabilities, contacted exchange partners and paused services while it investigated.

On Nov. 5, Binance said it had removed API keys linked to SignalPlus as a precaution. Binance said its systems were unaffected and customer funds remained safe. Deribit also revoked the linked keys and said its investigation found no indication that its systems or data had been affected. These are the exchanges’ own assessments. Neither statement amounts to a public, independent audit of every customer account.

SignalPlus initially estimated losses tied to the incident at below $82, 000 and said reimbursements had begun. Public statements cited in CryptoSlate’s reporting do not confirm the final reimbursement total or the number of users reimbursed.

Trading access can still put funds at risk

An API key is a credential that lets software make requests to an exchange account. Depending on the exchange, product and key settings, those requests may include reading account information, placing or canceling orders, or accessing other functions. The permissions assigned to the SignalPlus-linked keys have not been specified.

That uncertainty does not change the broader risk. A key with trading permission can expose an account to unwanted orders, losing positions, fees and execution costs, even if it cannot send cryptocurrency to an external wallet. Where leveraged products are available, trading can also trigger margin calls or liquidation, depending on the account and exchange rules.

Permission limits can restrict what software is allowed to do. They cannot make a strategy safe or prevent losses from bad trades, poor execution or a compromised service using its legitimate access.

Revoking a key is only the first step

Revoking an API key stops future requests made with that credential. It does not undo completed trades. Customers should not assume it automatically cancels every order or closes every position the software may have created.

Binance and Deribit told users to review orders and positions directly in their exchange accounts. Check recent activity and confirm whether any orders are still active. A third-party dashboard may not show the full picture once its connection is disabled.

SignalPlus said it had shut down its service for all associated accounts, including those where it had not identified unusual activity. The company planned to restore services in phases after system reviews and security upgrades, but the statements cited by CryptoSlate did not give a confirmed restoration timeline. Binance told customers to wait for SignalPlus to confirm the issue was resolved before reconnecting.

IP allowlisting helps, but it is not a force field

SignalPlus acknowledged that it had not made IP whitelisting mandatory and said affected accounts lacked the restriction. IP allowlisting limits API requests to approved internet addresses. It can block someone who has copied a key and tries to use it from an unapproved location.

But allowlisting alone cannot secure an approved device or network. If an attacker controls a trusted machine, requests may still appear to come from an allowed address. SignalPlus said it was strengthening API-access requirements and planned improvements to whitelist verification, employee-device protections, internal controls and key management.

In a Nov. 5 statement, SignalPlus said: We take responsibility for this oversight, referring to its failure to require IP whitelisting.

Practical steps for trading-service users

  • Check your exchange settings. Confirm the permissions assigned to each API key. Do not assume a key is limited to trading or that every exchange offers the same safeguards.
  • Revoke exposed or unnecessary keys. Binance and Deribit said they had already revoked SignalPlus-linked keys. Check your own exchange settings to confirm a key is no longer active.
  • Use IP restrictions where available. Treat allowlisting as one layer of protection, not a substitute for securing devices and networks.
  • Limit what a service can reach. If your exchange supports separate portfolios or accounts, consider keeping a connected trading account apart from other holdings, subject to the exchange’s rules.
  • Inspect the exchange directly after an incident. Review open orders, positions and recent activity instead of relying only on a bot’s dashboard.
  • Reconnect cautiously. Do not create replacement keys or reconnect a service until you have verified that it is safe and understand what has changed. If you reconnect, grant only the permissions it needs.

Binance founder Changpeng Zhao separately urged SignalPlus users to revoke related keys on other exchanges. He also advised against storing API keys with third-party platforms. That was personal guidance, not a blanket Binance instruction. Many trading services rely on API access, so the practical choice is not always “use no third parties.” Assess the service carefully, restrict its permissions and remember that automation adds another system you need to secure.

Key questions and answers

  • Can a trading bot lose money without withdrawal access?

    Yes. Trading permission can let software place orders that lose value or incur fees, even if it cannot transfer assets out of an exchange.

  • Were the SignalPlus-linked keys confirmed to be trading-only?

    No. SignalPlus and the exchanges did not publicly specify the permissions assigned to the affected keys.

  • Did Binance or Deribit say its systems were compromised?

    No. Binance said its systems were unaffected, and Deribit said it found no indication that its systems or data had been affected.

  • Does revoking a key cancel orders or close positions?

    Do not assume it does. Revocation stops future requests made with that key. Check the exchange directly to see whether orders remain active and what positions are open.

  • Does IP allowlisting prevent every API-key attack?

    No. It can reject requests from unapproved addresses, but may not help if an attacker controls an approved device or network.

Binance

Share this article

Powered by ADBYTES

Advertise smarter.

Adbytes.Media is a transparent advertising network where advertisers reach real audiences and publishers, affiliates & everyday members earn ADBYTES tokens. Join the community and start earning today.

Back to Blog