VVARB
arbitrage terminal
Sign in Sign up
Strategies 4 min read

Binance Cuts SignalPlus API Keys: Arbitrage Risks

Binance revoked SignalPlus API keys over a potential security issue. What it means for arbitrage bots, hedged positions and how to lock down your own keys.

Binance Cuts SignalPlus API Keys: Arbitrage Risks
+40% subscription days for new users

Pay for your first subscription within 24 hours of signing up and get extra days as a gift.

Sign up

What happened

Binance has removed trading connections to the third-party platform SignalPlus and cut off the API keys linked to it. The trigger was a warning about a "potential security issue" at SignalPlus itself. Binance says its own systems and user funds are unaffected and calls the move a precaution. It is urging users to check their accounts.

The cutoff comes a week after Binance lost billions in a hack blamed on North Korea. Since then the exchange has been acting fast on warning signs: it revokes access first and investigates afterwards. Anyone trading through external tools should expect similar cutoffs to arrive without notice.

Why arbitrage traders should care

Cross-exchange arbitrage runs almost entirely on APIs. Bots, trading terminals and hedge managers connect with a key and place and cancel orders on their own. When that key is revoked without warning:

  • the bot can no longer manage orders or positions on that exchange;
  • resting limit orders stay in the book and can fill without the other leg;
  • in a delta-neutral pair, one leg keeps running with nobody watching it.

Take a short perpetual on Binance hedged by a long on another exchange, both managed by a third-party terminal. Once the key is gone, the terminal loses sight of the Binance position. If its logic then closes the leg on the second exchange, the trader is left with a naked short, a directional position that can be liquidated. Spot-futures basis trades and funding carry face the same problem when external software runs them.

The second risk comes from the platform itself. If a service storing your keys is compromised, someone else may use them. A known pattern: an attacker uses victims' balances to buy an illiquid coin, pushes the price up and sells their own bags into it. That needs only trading permission, with no withdrawal access at all.

What to check right now

If you have ever connected an exchange account to an outside service, go through this list:

  • API management. Delete keys you no longer use and keys held by services you no longer trust.
  • Key permissions. Withdrawals should be off for any key stored outside your own machine.
  • IP whitelist. A key without an IP restriction works from anywhere. Bind it to your server addresses.
  • Open orders and positions. Compare them with what the bot is supposed to hold, and cancel stray orders on thin pairs.
  • Trade history. Look for buys of coins you don't trade, especially small caps.
  • Login security. Check 2FA, the anti-phishing code and active sessions.

Building pairs that survive a key cutoff

Treat a revoked key as a scenario in your risk model. These habits limit the damage:

  • Exchange-side stops. A conditional order placed on the exchange fires even when your bot is offline. On a perpetual leg, that is your liquidation insurance.
  • Margin buffer. In cross-exchange futures pairs, keep leverage low enough to close a leg by hand without rushing.
  • Manual access. Make sure you can log into every exchange from your phone and close a position within minutes.
  • Sub-accounts. One sub-account per service caps the loss at that sub-account's balance.
  • Size limits. The bot should never open more than you are willing to hold unhedged.
  • Separate keys by task. Use different keys for trading and for withdrawals. A key with withdrawal rights is best kept away from third parties.

For spot arbitrage with coin transfers, withdrawals are part of the strategy. Automate them only with a key you hold yourself, bound to your IP.

Liquidity and spreads

There is no data on how many traders used SignalPlus, so it is too early to judge any market effect. The mechanics are simple, though. When a group of automated participants drops out of the book at once, some pairs can briefly thin out, and cross-exchange spreads sometimes widen. If you see such a gap, check order book depth and fees first. A spread on an empty book can vanish before your second leg fills.

Bottom line

Binance cut off SignalPlus as a precaution and says user funds are safe. For arbitrage traders, the follow-up is practical. Audit your key permissions and IP limits, reconcile open positions, and set exchange-side stops that work without your bot.

Questions and answers

Why did Binance cut off SignalPlus?
Binance cited a potential security issue at the SignalPlus platform. It says its own systems and user funds were not affected and that the move was a precaution.
What happens to my positions if my bot's API key is revoked?
Your positions and orders stay on the exchange, but the bot can no longer manage them. In a hedged pair one leg may be left unattended, so check it and close it manually if needed.
What permissions should an arbitrage bot's API key have?
Give it trading and read access only, and bind it to your server's IP. Avoid giving withdrawal rights to keys stored with third-party services.

News source: CoinDesk

Find trades like these yourself

Staking and listings - a 3-day trial. Other screeners - demos delayed by 6-8 hours.

Read also