Fact-check findings
What an automated fact-checker found when it re-read Transit Finance 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
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: October 2022 Exploit
“SlowMist confirmed the root cause as the routing proxy's failure to inspect user-provided parameters, and noted the attack was linked to a legacy code issue originating from an old contract on TRON.”
reviewerSlowMist confirmed the root cause and linked it to legacy TRON codeMedium blocked the fetch. This is consistent with the widely reported root cause but I did not confirm it. - #5[unverifiable][awaiting moderator]in section: On-Chain Evidence and Laundering via Tornado Cash
“The BNB Chain exploit transaction is 0x181a7882aac0eab1036eedba25bc95a16e10f61b5df2e99d240a16c334b9b189”
reviewerAttacker address and exploit transaction hashesOn-chain addresses and hashes were not checked against an explorer or the (blocked) SlowMist post. - #8[unverifiable][awaiting moderator]in section: Protocol Overview
“CertiK Skynet assigns Transit Swap a score of 61.66 (B rating, approximately ranked #597) as of 2026”
reviewerCertiK Skynet score of 61.66 (B)Skynet is a dynamic JS page and I did not retrieve it. A live score will drift over time.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in the timeline
“By October 10, 2022 the attacker transfers 10,000 BNB (about $2.74M) to victims and separately routes 2,500 BNB (about $686K) to Tornado Cash.”
reviewerAttacker sent 2,500 BNB (about $686K) to Tornado Cash and 10,000 BNB (about $2.74M) went to victims by Oct 10, 2022Figures are correct. Search snippets indicate the 2,500 BNB was a negotiated bounty under a settlement in which Transit agreed not to pursue legal action. The page's 'separately' wording and 'attacker's conduct' framing may understate that Transit agreed to it. I could not read the full article body to confirm. - #3[partially supported][awaiting moderator]in the timeline
“Transit Finance sends an on-chain message offering the attacker a bug bounty with a 48-hour window, commits to fully compensating affected users and states the current contract version is unaffected (May 13, 2026).”
reviewerMay 2026 TRON legacy contract exploit, about $1.88M, with Transit committing to full compensationCompensation pledge and current-version statement are confirmed. The 48-hour bounty window and the amounts were not confirmed by the sources I could read (the Crypto Times page returned 403). - #6[partially supported][awaiting moderator]in section: On-Chain Evidence and Laundering via Tornado Cash
“One passage on the transit-finance page says the attacker framed '10,000 BNB sent to Tornado Cash' as a bug bounty, a characterization researchers and outlets did not accept; elsewhere the same page and the other sources say 10,000 BNB went to victims and 2,500 BNB to Tornado Cash.”
reviewerThe page's description of its own sources: 'the transit-finance page' and 'transit-swap' as sourcesThe factual split is right. The sentence refers to internal input pages ('the transit-finance page') as if they were sources, which is process leakage and not an encyclopedic citation. The same applies to 'transit-swap' in the recovery section and 'input pages' in the May 2026 section.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“about 70% was returned and part of the remainder was routed through the then-OFAC-sanctioned Tornado Cash mixer”
reviewerRoughly 70% of the stolen funds (about $18.9M of $28.9M) was returned within daysCoinDesk supports the 70% return. The Tornado Cash portion is supported by the 2022-10-10 CoinDesk article. - #7[confirmed][no action needed]in section: On-Chain Evidence and Laundering via Tornado Cash
“it was delisted in April 2025 following a Fifth Circuit ruling in December 2024 that limited OFAC's authority over immutable smart contracts”
reviewerTornado Cash delisted April 2025 and Fifth Circuit ruling in December 2024Consistent with my background knowledge: the Fifth Circuit ruled on Nov 26, 2024 (Van Loon v. Treasury), and the delisting was announced on March 21, 2025, effective in March 2025. The page's 'December 2024' and 'April 2025' are slightly off. I did not fetch a source, so I have no supported correction to propose and verdict is left as noted rather than disputed. Flag for human check.