Elliptic: $149M of Binance‐hack BTC rapidly moved into coinjoin mixers since Nov 17
Published · Updated
Linked reporting · 3 sources
News summary · AI-generated summary. No named staff review is recorded for the current text.
What happened
Elliptic ’s live analysis shows roughly 2,310 BTC linked to the October 29 Binance breach entered coinjoin mixers, with around 90% of that volume introduced since 17 November and daily peaks near $38 million. Attackers also moved large ether holdings from five wallets beginning 17 November; the FBI has named TraderTraitor as responsible and some funds have been frozen or seized.
- Severity
- Critical
What to do
- 1 Check law‐enforcement disclosures (the FBI published attacker addresses) before interacting with any suspicious on‐chain funds.
- 2 Do not accept or move funds from addresses publicly linked to the theft; report any deposits or counterparty links to your exchange or platform.
- 3 If you identify addresses or transactions tied to the incident, preserve evidence (transaction IDs, timestamps) and share it with relevant authorities or the forensic firm cited.
Written by AI from the sources, checked against them
Sources · 3 outlets
- The BlockBinance hack laundering ramps up as $149 million in bitcoin mixed through coinjoins: Elliptic
- Crypto BriefingBinance hack laundering accelerates as $149M in Bitcoin passes through coinjoins, Elliptic says
- CryptopolitanBinance hack mixing speeds up, with 90% of $149M coinjoined since November 17
About these sources
Outlets may repeat the same announcement. This count is not independent confirmation. How sourcing works.
Event updates
This story is part of a developing event
Elliptic reports that roughly $149 million in bitcoin linked to the Binance hack has been routed into coinjoin mixers, with a notable increase in mixing activity from 17 November. The firm says little of the laundered bitcoin appears to have been converted to fiat to date.
Status not recorded · Last material update
Ask about this story
Optional follow-up questions. AI answers can make mistakes; check the sources above.