NEWS
Binance Unplugs SignalPlus and Puts Overlay Tools on Notice
Binance and Deribit cut SignalPlus API keys after a Teams-invite breach under $82,000, leaving options desks without overlay trading or monitoring.
Binance and Deribit revoked all API keys linked to SignalPlus on November 5 after a breach the options platform put at less than $82,000. Overlay trading through the tool stopped the same day. Both venues said their own systems were not hit.
Changpeng Zhao, Binance’s founder, told anyone using SignalPlus on other venues to pull those keys too, and said traders should not store exchange credentials with third-party platforms. That warning is the part that outlives the small loss figure.
A Dormant Laptop and a Fake Teams Invite
SignalPlus said the attack started with a compromised Telegram account that belonged to a contact at a third-party technology vendor. Posing as that contact, the attacker sent a SignalPlus engineer a fake Microsoft Teams meeting invite, took over the engineer’s computer, and stayed quiet on the machine.
In the early hours of November 4 the attacker used the engineer’s access to go after the company’s internal network. SignalPlus said it detected the activity, blocked the path it found, then asked its exchange partners to cut every linked key and put its terminal into maintenance.
THE BREACH TIMELINE
- November 4, early hours: The attacker uses the engineer’s access against SignalPlus’s internal network.
- November 4: SignalPlus says it contains the intrusion and asks partner exchanges to revoke linked API keys.
- November 5: Binance announces it has removed every SignalPlus-linked key and tells users to check positions on the exchange itself.
- November 5: Zhao tells users on other venues to revoke SignalPlus keys and not to store keys with third parties.
- November 5: Deribit says it has revoked the same class of keys and that trading, monitoring and automation through SignalPlus have stopped.
- November 5: SignalPlus publishes its incident note, puts losses at less than $82,000, and pledges to repay affected users in full.
Binance described the cut as an immediate precaution after SignalPlus reported a potential security issue, said user funds remained safe, and told customers to wait for SignalPlus to confirm a full fix before binding new keys.
Following a potential security issue reported by third-party platform SignalPlus, we have proactively removed all API keys linked to SignalPlus as an immediate precautionary measure.
Binance's own systems are unaffected. User funds remain safe.
If you used SignalPlus, please… pic.twitter.com/0HYYkTAW2p
— Binance (@binance) November 5, 2026
Yi He, a Binance co-founder, posted the same instruction and asked every third-party platform tied to Binance to review its controls and call the exchange if anything looked wrong. The language is calm. The action is an unplug-first rule: kill the connection, then talk.
Deribit Options Desks Lost Their Terminal Overnight
SignalPlus is not a retail grid bot. Formed in 2021, it sells an options dashboard, pricing, volatility tools, risk controls and automated market-making hooks that sit on top of exchange APIs. HashKey Holdings, on May 20, said a fund it manages led a $40 million Series B+ in the company, with HashKey Group putting in $20 million of that cash. The Hong Kong filing described SignalPlus as an institutional-grade crypto derivatives platform for options systems, automated market-making and structured products.
Deribit is where that stack mattered most. When the keys died, desks that ran the book through SignalPlus did not lose their Deribit accounts. They lost the screen that priced the chain, hedged the delta and watched the book.
WHAT STOPPED ON DERIBIT
- Trading: Orders that had been sent through SignalPlus could not go out on that path.
- Monitoring: Live position and risk views that depended on the overlay went dark.
- Automation: Bots and hedging routines tied to the revoked keys stopped.
- The terminal: SignalPlus paused its own services while it reviewed security and applied patches.
Deribit told those users to check open orders, positions and recent activity on Deribit itself, to enable IP allowlisting on any new key, and to wait for official word from SignalPlus before reconnecting.
We have proactively revoked all Deribit customer API keys connected to SignalPlus as a precaution, after SignalPlus informed us they were experiencing a potential security concern. Deribit systems and data were not affected.
If you were using SignalPlus to trade on Deribit, all…
— Deribit (@DeribitOfficial) November 5, 2026
Binance gave the same homework: log in on the exchange, review positions and open orders, and leave the SignalPlus link dead until the vendor says the issue is closed. A trading key with withdrawals turned off is still a loaded key. It can buy, sell and lever a book the owner did not intend to move.
Seven Days After a $6.43 Billion Theft
The cutoff landed seven days after attackers drained Binance hot wallets on October 29. Elliptic’s $6.43 billion Binance theft analysis put that as the largest crypto theft on record. Binance estimated the impact at about $6.3 billion and said it had reserved more than $6.34 billion of company funds to cover customers, a coverage pile that is not the same figure as Elliptic’s theft tally. Elliptic separately verified $2.85 billion frozen or seized, almost all of it stablecoins.
Binance’s own postmortem of that theft, as later summarized with the SignalPlus note, described fraudulent hiring interviews, malicious development software and a compromised internal AI tool that reached wallet signing. The entry rhymes with SignalPlus: an engineer’s machine, a social-engineering lure, then a jump onto internal systems. The scale does not.
TWO INCIDENTS, SIDE BY SIDE
| Item | SignalPlus, November 4-5 | Binance, October 29 |
|---|---|---|
| Entry point | Fake Teams invite after a vendor Telegram account was taken over | Compromised engineer laptop, with Binance later citing more breach points |
| Losses | Less than $82,000, with SignalPlus pledging full repayment | $6.43 billion stolen per Elliptic; Binance reserved more than $6.34 billion to cover customers |
| Venue systems | Binance and Deribit said theirs were not affected | Binance hot wallets drained across multiple chains |
| What got cut | Every customer API key linked to SignalPlus | Withdrawals paused while the exchange rebuilt the path out |
Nothing in the public notes ties the two intrusions together. The timing still explains the speed. A venue that just spent a week covering a multi-billion-dollar theft does not give a third-party terminal the benefit of the doubt.
Borrowed API Keys Now Come With a Kill Switch
SignalPlus integrated Deribit in late 2022 so users could bind a Deribit API key and trade options, run volatility analytics, and use modules such as dynamic delta hedging from one dashboard. That design is the product. It is also the risk. The overlay holds live credentials that can move a book on the real exchange.
Once Binance and Deribit pull those credentials, the overlay has nothing to say to the matching engine. The accounts remain. The positions remain. The shared screen does not. SignalPlus said cutting a key does not mean the linked account data or assets were stolen, and that the precaution covered every user, including people whose accounts were not flagged as hit.
WHAT WE KNOW
- The loss figure: SignalPlus put total losses at less than $82,000 and said repayment had already started case by case.
- The venues: Binance and Deribit said their systems and, in Deribit’s case, their data were not affected.
- The gap: SignalPlus had not made IP whitelisting mandatory for exchange API access.
- The instruction: Users were told to manage positions on the exchanges and wait for SignalPlus before rebinding keys.
WHAT IS UNCONFIRMED
- Account count: SignalPlus has not published how many accounts were touched or how many keys the exchanges killed.
- Other venues: Zhao warned about every exchange, but only Binance and Deribit have described their own cuts in public.
- Restore date: SignalPlus said it expected a phased return over the following days and did not name a day.
- Unauthorized trades: The company has not published a line-by-line list of what the attacker did inside the affected accounts.
Users who think they were hit were asked to contact SignalPlus so the firm could check the claim and pay it. Everyone else was told to sit on the native exchange screens until the vendor finishes its review.
How 3Commas Taught Exchanges to Pull the Plug
This kill-switch is not new. On December 28, 2022, a Pastebin post claimed access to API data stored by 3Commas, the trading-bot platform. 3Commas confirmed the next day that some users’ API keys, secrets and passphrases had been disclosed by a third party, and that attackers could connect those exchange accounts or place trades. In its notice, the company asked exchanges to revoke connected keys at Binance, KuCoin and other supported venues, and told users to reissue keys.
The 2022 playbook and the 2026 playbook match. A third-party tool that stores exchange keys has a bad day. The exchanges invalidate the keys. Trading that depended on the tool stops until someone builds a new key, with tighter permissions, and plugs it in again. The difference this time is speed and posture. SignalPlus says it called the venues itself. Binance and Deribit moved in public within hours of that call. Zhao did not stop at one vendor.
A stolen trading key rarely needs a withdrawal permission to hurt. The 3Commas cases turned on unwanted orders, not an empty withdrawal queue. That is why Binance’s note spent as much time on open orders as on funds.
SignalPlus Left IP Whitelisting Optional
IP WHITELISTING
- The control: An exchange API key can be locked so it only works from named internet addresses.
- The point: A leaked key is much less useful if the venue rejects every request that is not on that list.
- The miss: SignalPlus said it had not required this lock as a condition of connecting exchange keys, and called that a failure it should have enforced.
The firm already told Deribit users which addresses to paste. Its Deribit API key setup guide lists SignalPlus system IPs and a static proxy address from a sales contact. The list existed. The mandate did not. SignalPlus said the accounts that were hit were a small set that had not set IP whitelists.
We take responsibility for this oversight.
SignalPlus, November 5 incident statement
It said it will tighten API access rules, harden development devices, raise internal access controls, change key management, and share more threat data with exchanges, vendors and security firms. Binance, in the same cycle, told every integrated third-party platform to review its controls and to call at the first sign of trouble. The checkbox that SignalPlus skipped is the same control both exchanges are now reciting in public.
Zhao’s Warning Reaches Every Options Overlay
Zhao’s post went further than a single vendor outage. He said Deribit had also reported the issue, and that Deribit had reported it first. Then he turned the incident into a rule for the category.
If you use SignalPlus for any other exchange platform, it’s time to revoke all your API keys. It is generally recommend that you do not store your API keys with any 3rd party platform.
Changpeng Zhao, Binance founder, on X
If desks follow that line, the overlay model has a problem that a patch cannot fix. The whole pitch is that a trader parks exchange keys with a specialist screen and lets that screen trade, hedge and watch. Zhao is telling them to keep the keys at home. Deribit still said users should only share keys with products they trust, which leaves a narrower door than Zhao’s wording, but the practical advice on November 5 was the same: do not reconnect until SignalPlus speaks, and turn on IP allowlisting when you do.
SignalPlus said it expected to bring services back in phases after a full review and patches, and that it would post user instructions on its official channels. It did not name a restore date. Until that all-clear comes, the people who actually lost something on November 5 are the options desks whose terminal went dark, staring at native Deribit and Binance screens while a vendor with a $40 million round and a four-year Deribit hookup rebuilds the lock it had left optional.
Disclaimer: This article is news reporting on a security incident at a trading tool and on actions taken by cryptocurrency exchanges. It is for information only and is not investment advice, trading advice, or a security assessment of any platform, API key, or account. Readers who connect exchange accounts to third-party software should consult a qualified information-security professional and, before moving funds or changing trading access, a licensed financial adviser. Loss figures, restore plans and account statuses come from the company and research statements cited here and may change as those investigations continue.
-
BUSINESS5 months agoAramco Crash Kills 14 Two Days After Oil Restart
-
NEWS6 months agoSalah Captained Egypt to Their First World Cup Win
-
GAMING2 months agoZelda’s 40th Switch 2 Ships Without a Zelda Game
-
NEWS3 months agoApple Labor Day Deals Hide June’s Memory Price Hike
-
NEWS4 months agoEl Niño Puts Israel’s Needed Winter Rain on a Flood Clock
-
GAMING2 months agoPalworld 1.0.4 Adds Palpedia Search After the 1.0 Launch
-
NEWS4 months agoSaudi Visa Routes Split Nigerian Travelers Into Two Speeds
-
BUSINESS9 months agoBAE’s 60-Year Saudi Franchise Now Runs Through Taif
