Fact-check findings
What an automated fact-checker found when it re-read Rhea 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.
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.
- #3[disputed][awaiting moderator]in the timeline
“2026-04-18”
reviewerShevchenko on-chain message and quote dated 2026-04-18Coin Edition dates the message April 17; the Crypto Times source was blocked (403). The entry also bundles the April 18 fact-check, so the date is only partly wrong.Proposed correction (not yet applied)2026-04-17
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Protocol Response and Compensation Framework
“Alex Shevchenko was quoted as acknowledging the partial return of funds, stating on-chain: 'This was the right thing to do, sir. Thanks for returning the money.'”
reviewerQuote attributed to Shevchenko acknowledging the returnCited source blocked; the Coin Edition article quotes a different Shevchenko message. - #7[unverifiable][awaiting moderator]in section: Technical Vulnerability — Slippage Protection Bypass
“Step 1 converted 1,000 USDC into 999 AttackerToken with a minimum output of 999; Step 2 converted 999 AttackerToken back into 1 USDC with a minimum output of 1.”
reviewerIllustrative USDC/AttackerToken arithmetic described as a simplified illustrationLabeled as a simplified illustration. I did not fetch the Halborn source, and The Block describes the root cause differently (undercollateralized margin positions routed into fake pools). - #8[unverifiable][awaiting moderator]in section: Attacker Preparation and Execution
“The suspected attacker address on the NEAR blockchain begins with 31ac7a27.”
reviewerSuspected attacker address begins with 31ac7a27Not found in sources I read; the PANews source was not fetched.
stale
1 claimThe claim was accurate when written but events since have overtaken it.
- #1[stale][awaiting moderator]in the summary
“Approximately $9.2 million was subsequently returned or frozen, with the remainder still outstanding as of mid-2026; a compensation framework was announced but had not been finalized at the time of publication.”
reviewerRoughly 9.2 million dollars returned or frozen; remainder still outstanding as of mid-2026; compensation framework not finalizedPage implies a large unrecovered balance persisting to mid-2026; later reporting (April 22) shows near-full recovery with a small shortfall that the team pledged to cover. The 9.2M figure also differs from The Block (11.2M).Proposed correction (not yet applied)Approximately $9 million was returned or frozen in the days after the exploit (The Block put the figure at about $11.2 million by April 17). By April 22, 2026, QuillAudits reported the remaining shortfall at about $0.4 million, which Rhea Finance committed to cover in full.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: Fund Recovery and Freezing
“raising the total of recovered or frozen funds to roughly $9.2 million against the revised $18.4 million total loss”
reviewerFrozen USDT amount and total recovered/frozen figureSources disagree and figures changed over time; 9.2M is a page-derived sum not stated in a fetched source.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #5[confirmed][no action needed]in section: April 2026 Exploit — Overview
“Rhea Finance revised the total loss to $18.4 million — more than double the initial estimate”
reviewerRoot cause and loss figure ($18.4M vs $7.6M initial)Confirmed by The Block. - #6[confirmed][no action needed]in section: Attacker Preparation and Execution
“Between April 13 and 15, 2026, the attacker created a subject wallet and distributed funds across 423 unique intermediary wallets to obscure the trail.”
reviewerAttacker prep April 13-15, 423 wallets, eight poolsSupported.