Security incident tracker

2026 Crypto Exchange Security Incidents

Understand what happened, which assets were affected and how exchanges responded. Compare fund theft, system intrusion and data exposure, with clear distinctions between frozen funds, recovery and platform replenishment.

Explore the timelinePage updated 2026-11-11
At a glance

This tracker covers five 2026 incidents involving Binance, Bitget, Mercado Bitcoin, Prabang and Bithumb. Each entry identifies its source date and evidence type. Figures retain their original scope and are not added into an annual loss total.

Incidents covered5

4 fund-transfer incidents · 1 system-intrusion report

Exchanges covered5

Separate records for each exchange and incident

Content checked2026-11-09

Service status is dated within each entry

2026 security incident timeline

Fund theft

Mercado Bitcoin: hot-wallet incident and a read-only reopening plan

The exchange said it detected and contained a system security incident on November 2, then paused access, deposits and withdrawals. The update published on November 4 planned website access from November 9 for balances, statements and investments; transfers, withdrawals and trading would return only after each module passed security checks.

Phased reopening announced ·
Multi-chain fund theft

Binance: endpoint intrusion, multi-chain transfers and recovery update #9

Binance’s October 30 initial announcement estimated about $6.3B affected, suspended withdrawals, revoked affected address authorization and pledged coverage from SAFU and company funds. Recovery update #9 on November 6 continued reopening withdrawals by asset and network; deposits remained open.

Withdrawals reopening in phases ·
System intrusion and employee-data exposure

Bithumb: an internal-system breach, distinct from confirmed asset theft

Seoul Economic Daily reported on October 29 that Bithumb’s internal systems were breached on October 27, exposing executive and employee information while customer-data exposure was still being checked. Odaily also relayed Korean reporting of attacks on financial firms without a specific Bithumb customer-impact count.

Customer impact not disclosed ·
Unauthorized hot-wallet transfers

Prabang: abnormal hot-wallet withdrawals and a compensation pledge

Odaily’s Yonhap-based report and Seoul Economic Daily said Prabang detected abnormal hot-wallet withdrawals on October 24, activated its response and identified a security vulnerability, then reported the incident to authorities on October 26. Services were suspended in the October 29 reporting.

Services paused in cited report ·
Hot- and warm-wallet fund theft

Bitget: a third-party security-product vulnerability and forged withdrawals

Bitget’s official incident record says unauthorized transfers began from certain hot and warm wallets on September 24; reconciliation detected discrepancies and blocked withdrawal requests platform-wide. The final reconciled affected amount was about $388M, and phased withdrawal recovery was completed on October 2.

Incident withdrawal recovery completed ·

Binance in focus: separate the attack path from fund recovery

A single loss figure cannot explain the incident. Endpoint compromise, on-chain authorization, asset freezes and service recovery answer different questions.

01

01 · Endpoints and privileged access

Binance’s initial findings point to a DevOps laptop and service container. ChainCatcher’s November 4 report describes a longer sequence involving a tampered installer in June, a recruitment coding assignment in September and access to another employee endpoint. These remain descriptions of the cited investigation stage.

02

02 · A valid signature does not settle the root cause

GCSA’s analysis published by ChainCatcher reviewed selected Ethereum transactions and EIP-7702 authorizations. On-chain evidence can show authorization and transfers, but cannot by itself establish whether a key was stolen or reconcile losses across every chain.

03

03 · Containment, freezes and reopening proceed separately

Revocation stops subsequent delegated execution; issuer freezes restrict movement of specific tokens; company replenishment supports liability coverage; reopening requires asset- and network-specific readiness checks. None of these steps substitutes for the others.

Total impactAbout $6.3B

Binance’s October 30 initial estimate; not final net loss.

Freeze snapshotAbout $3B

Binance’s October 30 measure; not additive with later valuations.

Company replenishment95%

Share of impacted amount replenished in the November 1 notice; not a recovery rate.

Later reopening2026-11-06

Update #9 reopened pairs progressively, not all assets simultaneously.

Major crypto exchange security incidents

Mercado BitcoinFund theft

Mercado Bitcoin: hot-wallet incident and a read-only reopening plan

Incident date stated by the exchange; an exact UTC start time was not disclosed.

Phased reopening announced
The exchange said it detected and contained a system security incident on November 2, then paused access, deposits and withdrawals. The update published on November 4 planned website access from November 9 for balances, statements and investments; transfers, withdrawals and trading would return only after each module passed security checks.
Amount snapshot

About $36.3M

Assets and scope

Reporting describes hot-wallet assets across several chains. The exchange has not published a complete asset-by-asset reconciliation; recorded account balances and withdrawal availability are separate matters.

User impact

The exchange pledged to replenish affected assets with its own resources. A plan to restore balance viewing does not mean withdrawals have fully resumed; account holders should keep statements and check official service notices.

Cause status

The cited statements confirm a system security incident but do not disclose a complete technical intrusion path. Timing alone does not establish a link to the Binance attack.

Freeze, recovery or replenishment

The November 3 official post reported $12.9M blocked. The update dated November 4 raised that figure to more than $15M and said repatriation efforts continued. Blocking assets does not establish that funds have been returned or credited to customers.

Response

  1. Paused platform access, deposits and withdrawals, activated security and governance procedures, and notified authorities.
  2. Worked with Tether, Circle, Paxos, BRL1, Chainalysis and others on tracing and asset freezes.
  3. Announced a read-only first phase before trading and transfers; the platform committed to fund replenishment.

Key dates

  1. Incident detected; services paused

    The exchange said it detected a system security incident and activated its response.

  2. Affected and blocked values updated

    Official post: about $36.3M affected and $12.9M blocked.

  3. Reopening plan announced

    The update dated November 4 planned website balance viewing for November 9, with other functions subject to validation.

BinanceMulti-chain fund theft

Binance: endpoint intrusion, multi-chain transfers and recovery update #9

On-chain transaction date in UTC; October 30 dates in Chinese reporting may use UTC+8.

Withdrawals reopening in phases
Binance’s October 30 initial announcement estimated about $6.3B affected, suspended withdrawals, revoked affected address authorization and pledged coverage from SAFU and company funds. Recovery update #9 on November 6 continued reopening withdrawals by asset and network; deposits remained open.
Amount snapshot

About $6.3B

Assets and scope

The incident involved exchange-wallet assets across multiple chains. The first reopening list included BTC, ETH, USDT, USDC, BNB and SOL, among others; a reopening list describes service availability, not a complete stolen-asset inventory.

User impact

The withdrawal interruption was a concrete service impact. The platform pledged to bear the financial loss, but that pledge does not imply immediate withdrawals for every asset and network; check its withdrawal interface and network-status page.

Cause status

The initial platform investigation pointed to a compromised DevOps laptop, access to a service container and unauthorized withdrawal submissions; it said no evidence of a wallet private-key leak had been found. A November 4 ChainCatcher report added an account of a tampered installer, recruitment pretexts and multiple employee endpoints. The final technical post-mortem remains the basis for a complete root-cause conclusion.

Freeze, recovery or replenishment

The official roughly $3B on-chain freeze figure on October 30 was a snapshot; subsequent Elliptic research used a different roughly $2.85B frozen-or-seized measure. On November 1 Binance said company resources had replenished about 95% of the impacted amount. Freezes, replenishment and actual recovery are distinct metrics.

Response

  1. Containment: suspend withdrawals, revoke affected address authorization and review wallet and signing infrastructure.
  2. Tracing and replenishment: work with law enforcement and blockchain investigators while using company and SAFU resources to cover the impact.
  3. Recovery: complete security checks for each network-asset pair, with a first phase on November 1 and further reopening in update #9 on November 6.

Key dates

  1. Unauthorized transfers appear on-chain

    GCSA’s analysis published by ChainCatcher records a Binance 14 EIP-7702 authorization transaction at 20:20:59 UTC; this is not the start of the entire intrusion.

  2. Initial platform disclosure

    About $6.3B affected and about $3B frozen; withdrawals paused and the platform pledged to cover losses.

  3. First reopening phase and replenishment

    The official first-phase window was 06:00–09:00 UTC; the same announcement reported roughly 95% replenishment of the impacted amount.

  4. Further intrusion details reported

    ChainCatcher relayed an investigation account of compromised endpoints, recruitment pretexts and a months-long intrusion; this is reporting, not a final independent audit.

  5. Recovery update #9

    The announcement set progressive reopening from 04:00 UTC for more assets on BSC, Base, Ethereum, Optimism and other networks, not simultaneous access for all pairs.

BithumbSystem intrusion and employee-data exposure

Bithumb: an internal-system breach, distinct from confirmed asset theft

System-breach date reported by Korean media; an exact UTC time was not disclosed.

Customer impact not disclosed
Seoul Economic Daily reported on October 29 that Bithumb’s internal systems were breached on October 27, exposing executive and employee information while customer-data exposure was still being checked. Odaily also relayed Korean reporting of attacks on financial firms without a specific Bithumb customer-impact count.
Amount snapshot

Asset loss not disclosed

Assets and scope

The reported scope concerns internal systems and employee information; customer-data and asset impacts require separate verification.

User impact

Data exposure can increase impersonation and targeted-phishing risks. Customer impact should be checked against platform notices; employee-data exposure does not itself establish theft of customer assets.

Cause status

The cited reporting does not disclose the specific vulnerability or intrusion path; incidents at other Korean firms do not establish a shared cause.

Freeze, recovery or replenishment

No verifiable fund-freeze, recovery or compensation amount is disclosed. This entry is excluded from any fund-theft total.

Response

  1. At the reporting date, authorities were assessing the incident and the platform’s customer-impact scope was not fully public.
  2. Retain the system-intrusion classification; do not substitute zero for an undisclosed loss or assign another company’s data-leak count to this incident.

Key dates

  1. Internal-system breach

    Incident date given in subsequent Seoul Economic Daily reporting.

  2. Employee-data impact reported

    Reporting said customer-data exposure was still being checked; no stolen-asset amount was disclosed.

PrabangUnauthorized hot-wallet transfers

Prabang: abnormal hot-wallet withdrawals and a compensation pledge

Korean local date on which the exchange detected anomalies; an exact UTC time was not disclosed.

Services paused in cited report
Odaily’s Yonhap-based report and Seoul Economic Daily said Prabang detected abnormal hot-wallet withdrawals on October 24, activated its response and identified a security vulnerability, then reported the incident to authorities on October 26. Services were suspended in the October 29 reporting.
Amount snapshot

About KRW 100M

Assets and scope

Customer assets in an internet-connected hot wallet were affected; the cited reports do not give a complete list of tokens and quantities.

User impact

The service suspension affected trading and access to assets. A compensation pledge, actual crediting and service restoration are different milestones and should not be summarized as a resolved incident.

Cause status

Unauthorized external access and a hot-wallet security vulnerability were reported, with the precise technical path under investigation. Reporting distinguished this fund-loss incident from an earlier separate data leak.

Freeze, recovery or replenishment

The platform said it would cover verified losses in full using company assets; the cited sources do not confirm completed compensation or recovery.

Response

  1. Activated incident response and suspended services after detecting hot-wallet anomalies.
  2. Reported the incident on October 26 and investigated the cause and scope.
  3. Pledged compensation from company assets; completion requires a subsequent platform notice.

Key dates

  1. Abnormal withdrawals detected

    Hot-wallet anomalies triggered the emergency response.

  2. Authorities notified

    The platform reported unauthorized external access to authorities.

  3. Loss and compensation plan reported

    A preliminary KRW 100M loss and full-compensation pledge were reported; completion was not confirmed.

BitgetHot- and warm-wallet fund theft

Bitget: a third-party security-product vulnerability and forged withdrawals

First unauthorized transfers at 18:31 UTC; reconciliation detected anomalies at 19:05 UTC.

Incident withdrawal recovery completed
Bitget’s official incident record says unauthorized transfers began from certain hot and warm wallets on September 24; reconciliation detected discrepancies and blocked withdrawal requests platform-wide. The final reconciled affected amount was about $388M, and phased withdrawal recovery was completed on October 2.
Amount snapshot

About $388M

Assets and scope

The platform lists 11 chains and 12 assets, including XRP, ETH, USDT, ZEC and USDC. It says cold wallets were unaffected and private keys were not compromised.

User impact

Withdrawals were interrupted; the platform says deposits, trading and account balances were unaffected. BTC, ETH, USDT and other supported assets returned in sequence. Completion on October 2 refers to this incident’s recovery plan, not a guarantee against later network maintenance.

Cause status

The platform attributes the attack to a zero-day vulnerability in a third-party security product: stolen privileged internal credentials enabled forged wallet withdrawal instructions that bypassed risk controls. This is the platform’s investigation finding.

Freeze, recovery or replenishment

The platform says its Protection Fund covers the impact and was replenished above $300M by September 30. Tracing and recovery continued; fund replenishment is not counted as recovered stolen assets.

Response

  1. Remediated the vulnerability, reset internal credentials, restricted sensitive access and strengthened independent withdrawal verification.
  2. The platform states that Mandiant and SlowMist published independent reports on September 30 consistent with the disclosed attack path.
  3. Withdrawals resumed in stages: BTC on September 28, ETH on September 29, USDT on September 30, and remaining supported coins plus fiat/P2P on October 2.

Key dates

  1. Unauthorized transfers and containment

    First unauthorized transfers at 18:31 UTC; reconciliation detected anomalies and blocked withdrawals at 19:05 UTC.

  2. BTC withdrawals restored

    ETH followed on September 29 and USDT on September 30.

  3. Phased recovery completed

    The official record says remaining supported coins, fiat and P2P resumed, completing the incident recovery plan.

How to read loss, recovery and service impact

First identify what was affected

Fund theft needs transfer or platform-reconciliation evidence; a data leak needs a defined population and data types; a service pause needs asset, network and restriction details. These can coexist but are not interchangeable.

Check the notice date and scope

Restoring BTC does not restore every asset, and balance viewing does not restore withdrawals. Check the asset, network, account region and notice date, and retain balance and transaction records.

Distinguish a pledge from completion

“The platform will cover it,” “reopening planned” and “funds frozen” describe a coverage pledge, a service plan and an asset-control state. Completed compensation needs crediting or fulfillment evidence; recovery needs return or lawful-control evidence.

Watch for post-incident impersonation

Use your saved official site and check security notices. Do not provide seed phrases, verification codes or payments to unsolicited messages offering unfreezing or compensation; a recovery notice does not require third-party wallet verification.

  • Scope: publicly disclosed 2026 centralized-exchange fund-security incidents, system intrusions and directly related data incidents. This is a selected tracker, not an exhaustive annual inventory.
  • Evidence: prioritize platform statements, supplemented by ChainCatcher, Odaily and named reporting. Identify media relays, platform claims and independent research separately; syndicated reports are not independent confirmations.
  • Dates: use UTC where a source supplies an explicit timezone; retain and label local calendar dates otherwise. A status date identifies the cited notice, not a live service check.
  • Amounts: retain currency, units, valuation time and source. Distinguish freezing, seizure, recovery and platform replenishment; missing values are not zero and incompatible estimates are not subtracted to produce net loss.
  • Updates: revise the entry, timeline and FAQs when a technical post-mortem, reopening notice or verified financial revision appears; do not redate past incidents as new events.

Frequently asked questions

Which exchanges had security incidents in 2026?

This page records fund-transfer incidents at Binance, Bitget, Mercado Bitcoin and Prabang, plus reporting on a Bithumb system intrusion. It is not an exhaustive annual list; each entry explains its type and evidence basis.

How much was affected in the Binance incident?

Binance’s October 30 notice initially estimated about $6.3B affected; later Elliptic research used about $6.43B. Valuation and scope differ, so neither should be presented as final net loss.

Do frozen funds count as recovered funds?

No. A freeze restricts movement; recovery requires evidence of return or lawful control. A platform replenishing assets from its own funds is also different from recovering funds from an attacker.

Have all Binance withdrawals resumed?

The November 6 official recovery update #9 still describes progressive reopening by asset and network and says the listed pairs do not all become available at once. Check the official withdrawal or status page for a specific pair.

Why did Bitget’s figure change from $351.6M to $388M?

The $351.6M figure came from an early September 25 response. Bitget’s official page updated October 13 lists about $388M after final reconciliation and 12 wallet addresses. Figures from different investigation stages need their dates.

What did Mercado Bitcoin plan to restore on November 9?

The platform’s update dated November 4 planned website access to balances, statements, assets and investments first. Transfers, withdrawals and trading would follow after security validation; read-only access is not full service restoration.

Did the 38,490-person information leak involve Bithumb?

No. The 38,490 customers in the same Odaily story belong to Daishin Securities; Bithumb’s customer scope was undisclosed at that point. Seoul Economic Daily separately reported exposure of executive and employee information.

Crypto asset prices can fluctuate significantly. This information is for research purposes and does not constitute investment advice.