HEI

Historical Exchange Index

A quiet registry of crypto exchanges, active and gone.

Home / Active / BigONE

Exchange record

BigONE

Centralized exchange that suffered an approximately USD 27 million supply-chain / hot-wallet breach in July 2025. The exchange said private keys and cold storage remained safe, pledged full user compensation, and described service restoration rather than a terminal shutdown.

CEXActive
Also known as: BigONE Exchange

Registry sequence

Key facts

Launch date
2017-01-01
Death date
Years
2017–—
Origin
Seychelles / Global
Confidence
medium
Last verified
2026-04-26

URL handling

Preferred action
Use current URL handling based on status below.
URL status
Live unverified
Original URL
Archived URL

Summary

Centralized exchange that suffered an approximately USD 27 million supply-chain / hot-wallet breach in July 2025. The exchange said private keys and cold storage remained safe, pledged full user compensation, and described service restoration rather than a terminal shutdown.

Timeline

BigONE suffered a USD 27 million breach
2025-07-16hackcritical

BigONE confirmed a roughly USD 27 million hot-wallet / supply-chain breach, while stating that private keys and cold storage remained safe and that user balances would be fully covered.

BigONE deposits were temporarily suspended
2025-07-16deposit_suspendedhigh

BigONE temporarily suspended deposits while reinforcing system security after the breach, with later updates indicating deposit and trading services were restored.

BigONE trading was temporarily halted
2025-07-16trading_haltedhigh

Reporting described BigONE as temporarily freezing or suspending trading functions after the USD 27 million security incident while working with SlowMist to trace stolen funds.

Evidence

Tom's Hardware2025-07-16news_articlemedium reliabilityeventarchive
CoinSpice2025-07-16news_articlemedium reliabilityeventarchive

Notes and record state

Record note
Included because HEI tracks major state-changing exchange events, not only deaths. Keep entity active unless later evidence shows unresolved service failure or closure. The 2025 breach should be modeled through hack, deposit_suspended, and trading_halted events with limited event effects.
Revision state
Records may be incomplete, approximate, contested, or revised as better evidence becomes available.
This record may be incomplete or revised. Dead-side entries prefer archived URLs over original domains. Dates, causes, and classifications may change when stronger evidence becomes available. Contact / corrections

Navigation

Registry
Active-side
Contact / Corrections
GitHub Issues