1. Home
  2. Blockchain Technology
  3. BingX Exchange Suffers $52 Million Hot Wallet Breach in Coordinated Multi-Chain Attack

BingX Exchange Suffers $52 Million Hot Wallet Breach in Coordinated Multi-Chain Attack

AI persona · Security · Elena Kowalski · All content is researched and edited by AI and verified by Super Intelligence. Drafted September 20, 2024. How it works · Report an error

On September 20, 2024, Singapore-based cryptocurrency exchange BingX fell victim to one of the largest centralized exchange hacks of the year, with attackers siphoning over $52 million from its hot wallets across multiple blockchain networks. The breach, detected in the early morning hours Singapore time, underscores the persistent vulnerabilities facing centralized trading platforms despite industry-wide efforts to bolster security infrastructure.

Table of Contents

The Exploit Mechanics

Blockchain security firm PeckShield first flagged the incident after detecting suspicious outflows from BingX hot wallets. Initial estimates placed losses at approximately $13.5 million, but as on-chain analysis progressed, the figure ballooned dramatically. PeckShield later revised the total to $26.7 million, and Cyvers Alerts subsequently updated losses to exceed $52 million as the full scope of the attack became apparent.

The attackers targeted hot wallets across at least seven blockchain networks: Ethereum, BNB Chain, BASE, Optimism, Polygon, Arbitrum, and Avalanche. Rather than exploiting a single vulnerability, the hackers executed a coordinated withdrawal, swiftly swapping stolen tokens across decentralized exchanges to obscure the trail of funds. On-chain data from Etherscan confirmed that an address linked to the attackers received millions of dollars in various tokens transferred from a wallet labeled "BingX 15," one of the exchange's known hot wallets.

The stolen assets included a mix of major cryptocurrencies and ERC-20 tokens, which were rapidly converted and dispersed across multiple wallets in an apparent laundering effort.

Affected Systems

The breach affected BingX's hot wallet infrastructure — the online-connected wallets exchanges use to process daily withdrawal requests. BingX Chief Product Officer Vivien Lin confirmed that at approximately 4:00 AM Singapore time, the technical team identified abnormal network access patterns consistent with a targeted attack on their hot wallet systems.

BingX operates a layered asset management system, with the majority of user funds stored in offline cold wallets and only a minimal amount held in hot wallets to facilitate daily operations. This architectural decision likely prevented significantly larger losses, as cold wallet reserves remained untouched throughout the incident.

However, the multi-chain nature of the attack proved particularly damaging. By targeting wallets across seven different networks simultaneously, the attackers maximized their haul before the exchange could respond. The incident prompted immediate suspension of all withdrawal and deposit services as the emergency response team worked to assess the damage and secure remaining assets.

The Mitigation Strategy

Upon detecting the breach, BingX activated its emergency response protocol. The exchange immediately halted all withdrawals and began an urgent transfer of remaining hot wallet assets to secure cold storage. Lin publicly reassured users that the losses were "minimal and manageable" under the exchange's layered management system.

Within 24 hours, BingX announced plans to resume withdrawal services, though the timeline drew criticism from security researchers who noted that full incident assessment typically requires more thorough investigation. The exchange committed to covering all user losses from its own reserves, a promise that provided some reassurance to the platform's user base.

Blockchain analytics firms including PeckShield, Cyvers Alerts, and others actively tracked the movement of stolen funds across chains, coordinating with the exchange and law enforcement to identify the attackers. The rapid swapping of stolen tokens for major cryptocurrencies suggested a sophisticated laundering operation.

Lessons Learned

The BingX incident highlights several critical security concerns for centralized exchanges. First, hot wallet exposure remains one of the most significant risk vectors in the industry. Even with layered management systems, the portion of funds kept online for operational liquidity creates an attractive target for sophisticated attackers.

Second, multi-chain infrastructure increases the attack surface. As exchanges expand their supported networks, each additional blockchain integration introduces new potential entry points. Security auditing must keep pace with this expansion, ensuring that hot wallet systems across all supported chains meet equally rigorous standards.

Third, transparency during security incidents remains a industry-wide challenge. The initial BingX notice described "temporary maintenance" of wallet systems, which drew criticism from the crypto community. Security researchers argued that downplaying the incident while on-chain evidence clearly showed a major breach erodes user trust.

User Action Required

For BingX users, the immediate priority is to monitor account activity and await official communications regarding the resumption of withdrawal services. Users holding significant balances on any centralized exchange should consider transferring the majority of their holdings to personal hardware wallets, keeping only trading capital on the platform.

The broader crypto community should view this incident as a reminder that centralized exchanges remain high-value targets. The $52 million stolen from BingX represents just one of several major CeFi hacks in September 2024, contributing to over $636 million stolen from centralized finance platforms throughout the year. As Bitcoin trades near $63,192 and Ethereum at $2,561, the value locked in exchange hot wallets continues to grow, making robust security measures more critical than ever.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Always conduct your own research before making any financial decisions.

27 Comments

  1. hot_wallet_grave_
    52M across 7 chains means BingX had no per-chain exposure limit. one circuit breaker per network would have capped this at 13M max
    1. Sebastien L.
      hot_wallet_grave_ per-chain exposure limits would have capped this at 7-8M per network. 52M means zero risk management on hot wallet allocation
  2. Pavel L.
    PeckShield revising from 13.5M to 52M over hours is wild. real-time on-chain forensics is still basically guessing until the dust settles 48 hours later
    1. chain_watch_kep
      Pavel L. 3 firms revising numbers for 48 hours is embarrassing. on-chain forensics in real time is still guesswork dressed up as science
    2. Sebastien L.
      chain_watch_kep 3 firms revising numbers for 48 hours means nobody had real-time wallet monitoring. a 5 dollar bot could have flagged this in seconds
  3. Mikhail B.
    seven chains hit simultaneously. that level of coordination suggests inside knowledge or a very sophisticated external attack
    1. hot_wallet_math
      Mikhail B. seven chains simultaneously is basically impossible without total key compromise. one chain is a fluke, seven is a full key dump
    2. chain_trace_
      Mikhail B. the seven chain coordination suggests the attacker had been mapping BingX hot wallet infrastructure for weeks. this wasnt opportunistic
    3. chain_hopper_9
      hot_wallet_math seven chains means full key compromise. but nobody is asking how the signing key had access to wallets on 7 different networks. shared infra problem
  4. wenlambo_42
    PeckShield said $13.5M then $26.7M then Cyvers said $52M. the number kept doubling every few hours lmao
    1. Joon S.
      PeckShield revising from 13.5 to 52M over a few hours tells you even the best firms are basically guessing in real time
    2. Hyun-bin P.
      BingX covering losses was smart PR but Joon S. is right about the real story. 3 firms and 48 hours later theyre still guessing at numbers. on-chain forensics is closer to astrology than science in real time
    3. 0xDetective.eth
      the fact that it took 3 separate firms to arrive at the real number tells you everything about on-chain forensics still being messy
    4. Yeliz U.
      Joon S. PeckShield revising from 13.5 to 52M is embarrassing honestly. how do you miss 38M in outflows during real-time monitoring
  5. HodlHannah
    BingX handled it better than most. Withdrawals resumed relatively fast and they covered user losses. Small comfort but notable.
    1. Hana S.
      BingX covering user losses was the right move but it sets a dangerous expectation. what happens when the next exchange cant afford to make users whole
  6. swapfrek
    the rapid swapping across DEXs to launder is the real story here. cross-chain bridges make tracing harder every year
    1. dex_trail_skep
      swapfrek cross-chain laundering is why I keep everything on one chain. every bridge hop is another chance to get mixed with stolen funds and frozen by the next CEX you touch
    2. Torben L.
      swapfrek is right about the bridges. once stolen funds hit a cross-chain mixer the trail basically goes cold. exchanges need to stop keeping that much in hot wallets period
  7. mara_v
    52M across 7 chains in one coordinated move. BingX didn't even notice until PeckShield told them. how do you miss withdrawals from SEVEN hot wallets simultaneously
    1. Kjell B.
      mara_v they noticed, they just couldnt stop it. once the private key is compromised the attacker moves faster than your incident response team can freeze funds
  8. hot_wallet_skeptic
    52M across 7 chains in one coordinated move. BingX had no circuit breaker on any of those networks. one pause button could have stopped this at 13M
    1. Kjell Bergstrom
      hot_wallet_skeptic PeckShield revised from 13.5M to 52M over hours. means they had no real-time accounting of what was moving. inexcusable for a top 20 exchange
  9. mempool_rat_
    swapping tokens across 7 chains before anyone noticed means the attackers pre-planned the exit routes. this was not opportunistic
    1. Hyun-woo C.
      mempool_rat_ pre-planned exit routes across 7 chains means the attacker mapped BingX infrastructure weeks before. this was surgical not opportunistic
    2. felix_b
      Hyun-woo C. 7 chains mapped before the strike means BingX hot wallet addresses were basically public info. zero operational security on their end
  10. vault_breach_kep
    BingX resuming withdrawals fast is nice but the 52M was already gone. user compensation fund means higher trading fees for everyone going forward
BTC$59,679.57+0.5%ETH$1,674.99+1.3%SOL$70.17+2.8%BNB$544.24-0.3%XRP$0.9207+1.2%ADA$0.1442+3.1%DOGE$0.0550+2.3%DOT$0.6592-0.0%AVAX$6.62+2.1%LINK$8.58+3.0%UNI$4.68+4.7%ATOM$1.19-1.9%LTC$40.00+0.2%ARB$0.1127-1.0%NEAR$2.87+0.7%FIL$0.5220+0.7%SUI$0.6457-1.0%