Fact-check findings
What an automated fact-checker found when it re-read Orange 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
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in the summary
“The protocol was flagged by ZachXBT and has not resumed normal operations since the incident.”
reviewerOrange Finance was flagged by ZachXBTNeither the Rekt article nor the Web3 Is Going Great entry mentions ZachXBT, and the Telegram channel is a generic feed. I found no specific ZachXBT post about Orange Finance. - #5[unverifiable][awaiting moderator]in section: ZachXBT Flagging and Community Risk Assessment
“ZachXBT's investigations channel on Telegram, which tracks DeFi exploits and fraud cases, catalogued the Orange Finance incident as a significant access-control failure.”
reviewerZachXBT channel catalogued the incident as a significant access-control failureCitation is a channel root, so the claim cannot be checked against a stable item. - #7[unverifiable][awaiting moderator]in section: Team Response and Recovery Efforts
“The team engaged Seal 911, a DeFi emergency response group, to assist with the investigation.”
reviewerSeal 911 was engagedThe Mirror report was not fetched; Rekt does not mention it. - #9[unverifiable][awaiting moderator]in section: Security Failures: Operational and Architectural Deficiencies
“though Stryke reported retaining approximately 50% of TVL in secured positions”
reviewerStryke retained about 50% of TVLSearch results mention Stryke affected only on Orange vaults and about $731K retained; the 50% figure was not found.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #8[partially supported][awaiting moderator]in section: ZachXBT Flagging and Community Risk Assessment
“As of the available public record, no funds were returned by the attacker, no law enforcement action has been publicly announced, and the Orange Finance UI remains offline.”
reviewerNo funds returned and UI remains offline as of nowNo return of funds found, but the current UI state was not directly verified.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: January 2025 Exploit: Private Key Compromise and Contract Takeover
“On January 8, 2025, Orange Finance suffered a critical access-control exploit resulting in the theft of approximately $843,556.90 in user assets.”
reviewerApproximately $843,556 was drained after admin key compromise and single-signature multisig misconfigurationTotal, cause and date match. Rekt says the attack occurred on a Tuesday night, which may be Jan 7 in US time zones; the team announced it Jan 8. - #2[confirmed][no action needed]in section: January 2025 Exploit: Private Key Compromise and Contract Takeover
“Asset losses were distributed across multiple DEX platforms, with approximately $340,000 drained via Uniswap, $472,000 via PancakeSwap, and $20,000 via SushiSwap.”
reviewerLoss breakdown by DEX and by categoryRounded figures match. - #3[confirmed][no action needed]in section: January 2025 Exploit: Private Key Compromise and Contract Takeover
“The attacker address identified in on-chain analysis is 0x496e5a7ba67735c7ee5eb81ef07b65b909a31345”
reviewerAttacker address and Stargate exitAttack contract 0x17c8... not independently verified. - #6[confirmed][no action needed]in the timeline
“Orange Finance sends on-chain message to attacker's address offering white-hat arrangement with 24-hour deadline and guarantee of no law enforcement involvement.”
reviewerTeam posted warning, offered white-hat deal with 24-hour window and no law enforcementTimeline entry has an empty source field.