Fact-check findings
What an automated fact-checker found when it re-read Mixin Network against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #6[disputed][awaiting moderator]in the timeline
“https://www.bitget.com/news/detail/12560603893640”
reviewerOctober 2025 repayment update (MDTu ~$23M by Sept 2026; no timeline for MDTe/MDTb) is sourced to BitgetThe cited Bitget page is the February 2024 MDT launch article and does not support the October 2025 claim. A search snippet reports the claim (Sept 23, 2026 target for MDTu) but I did not fetch a primary source, so no replacement URL is proposed.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #10[unverifiable][awaiting moderator]in section: Regulatory status
“No enforcement action by the Hong Kong Securities and Futures Commission (SFC) or the U.S. Securities and Exchange Commission (SEC) targeting Mixin Network over the 2023 hack or its debt-token compensation scheme had been identified as of reporting”
reviewerLazarus Group attribution is unconfirmed; no charges or arrests; SFC/SEC no actionNegative claim; I found no contrary reporting, but did not fetch the compliance page or verify the FinCEN MSB reference.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in the timeline
“Elliptic and Merkle Science publish on-chain analyses (dated September 25 or 26 depending on the report)”
reviewerMerkle Science analysis published September 25 or 26The cited Merkle article is dated September 27, 2023, not 25 or 26. Elliptic's publication date was not verified. - #7[partially supported][awaiting moderator]in section: Fund recovery and user compensation
“In an October 2025 update, Mixin said MDTu, representing about $23 million of debt, was on track to be fully repaid by September 2026.”
reviewerSame Bitget source is cited in Fund recovery and Risk assessment for the MDTu October 2025 updateA search result summary reports the same update, but no fetched cited source does. The September 2026 deadline has now passed (today is 2026-10-27) and the page says 'on track' without saying whether repayment happened.
confirmed
6 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Exploit: September 2023 cloud database breach (~$200 million)
“Elliptic's on-chain analysis put the haul at approximately $95.3 million in Ether, $23.7 million in Bitcoin and $23.6 million in USDT, with the remainder in other assets, for a total loss of approximately $200 million”
reviewerHack occurred Sept 23, 2023 and about $200M was lost, with ETH $95.3M, BTC $23.7M, USDT $23.6MElliptic gives these exact figures and the September 23, 2023 date. - #2[confirmed][no action needed]in section: On-chain tracing of stolen funds
“Exploiter 1', which received approximately 59,807 ETH (roughly $94 million) in more than 10,000 transactions from over 11,400 ETH wallets”
reviewerMerkle Science exploiter figures (59,807 ETH, >10,000 txs, >11,400 wallets, ~23.5M USDT, 891 BTC from 127 wallets in 3 txs), USDT swapped to DAIMatches Merkle text. Elliptic confirms DAI swap and non-freezable rationale. - #4[confirmed][no action needed]in the timeline
“February 12: after more than two years of dormancy, the wallet tagged 'Mixin Hacker' by Arkham Intelligence sends 2,005 ETH (about $3.85 million) to Tornado Cash, routed through intermediate address 0x9cba859288Fa0b4eC43EBB90Bb64a9DbBDDc787f in 20 transactions.”
reviewerFeb 2026: wallet moved 2,005 ETH (~$3.85M) to Tornado Cash via intermediate address in 20 transactionsDecrypt lacks the 2,005 ETH figure but The Block supplies it. - #5[confirmed][no action needed]in section: Laundering through Tornado Cash (2026)
“After this movement the original attacker wallet still reportedly held about 57,849 ETH (approximately $113 million) and 891 BTC (approximately $59.7 million), together valued at over $170 million.”
reviewerRemaining holdings 57,849 ETH (~$113M) and 891 BTC (~$59.7M); three new wallets received 2,087 ETH sold at ~$1,933Figures are a February 2026 snapshot; the summary and risk text correctly say 'as of February 2026'. - #8[confirmed][no action needed]in the timeline
“Mixin Kernel launches the Mixin Debt Token (MDT) in three tranches (MDTu, MDTe, MDTb) for the 50% deferred repayment.”
reviewerMDT launched February 2024 in three tranches MDTu, MDTe, MDTbConfirmed via the Bitget article dated 2024-02-01. The cited Mixin support page was not fetched. - #9[confirmed][no action needed]in section: Fund recovery and user compensation
“The network did not shut down and continued to claim more than $1 billion in assets under management and over one million active users in subsequent months.”
reviewerMixin did not shut down and remains operatingConsistent with 2026 coverage.