Fact-check findings
What an automated fact-checker found when it re-read Chainflip TRON USDT Exploit (September 2026) 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.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in the timeline
“The team described the incident as its first significant critical vault loss.”
reviewerChainflip described the incident as its first significant critical vault loss, and publicly disclosed on 2026-09-13The disclosure date is confirmed. The 'first significant critical vault loss' wording was not located in the official post as fetched; the CryptoTimes article was not independently read.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #6[partially supported][awaiting moderator]in the cited sources
“http://web.archive.org/web/20260924184036/https://en.coin-turk.com/time-traveler-urges-xrp-wallets-before-key-senate-clarity-act-vote/?rbsnp=1”
reviewerArchive link for the Coin-Turk source in sources_used points to an unrelated articleThe stored archive_url is for a different article (XRP/Senate), so the archive does not preserve the cited page. The proposed replacement is an unverified generic Wayback pattern and the owner should capture a proper snapshot; I did not fetch it.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Exploit Mechanism
“The attacker executed this technique eight times over approximately 90 minutes on the morning of September 12, 2026. Six of the eight attempts produced unauthorized payouts.”
reviewerAttacker ran the exploit eight times over about 90 minutes; six produced unauthorized payouts totaling 736,442.17 USDTMatches the official incident report. Some secondary reporting is inconsistent on payout counts, but the primary source agrees with the page. - #2[confirmed][no action needed]in section: Financial Impact
“A seventh transaction involving 115,654.41 USDT — a legitimate in-flight user swap — remained unprocessed in the vault at the time of the halt and was described by Chainflip as recoverable upon a secure restart.”
reviewerA 115,654.41 USDT legitimate user swap remained in the vault and is recoverable on restartSupported. Calling it a 'seventh transaction' is the page's own framing. - #3[confirmed][no action needed]in section: Network Response and Patch
“version 2.2.13 restricts TRON vault swaps to accept only direct transfers to the Vault address, eliminating the memo-attachment vector used in the attack”
reviewerVersion 2.2.13 released around Sept 15 restricts TRON vault swaps to direct transfers and closes trxUSDT strategies, cancels pool orders, repays loans, and snapshots LP balancesRelease notes match. The 'eliminating the memo-attachment vector' phrasing is an inference but consistent with reporting. - #5[confirmed][no action needed]in section: Network Response and Patch
“TRON remained excluded from the restart with no confirmed reinstatement date disclosed as of late September 2026.”
reviewerMost routes restarted Sept 15-16 with TRON excluded; no reinstatement date or reimbursement funding source disclosedSearch as of 2026-10-27 found no later coverage of reinstatement, compensation or a post-mortem; the page's hedged 'as of late September' wording holds, though it is about a month old.