← SUNRAY·FINANCEreviewed 2026-11-02 · 14 claims checked
Fact-check findings
What an automated fact-checker found when it re-read SUNRAY·FINANCE against the sources the page cites. Only the most recent review is shown.
Read this first
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: Exploit Overview
“exploited contract address: 0xb1bbe57f5c474996a84274f0078a2411e1a65b8a”
reviewerExploited contract address 0xb1bb... is the management contractNone of the fetched sources state this address. The tx hash does appear in Quadriga. I did not check an explorer. - #11[unverifiable][awaiting moderator]in the timeline
“2024-11-30”
reviewerSunray website went offline on 2024-11-30No source gives a specific offline date. The exact day looks invented. Offline status is supported only as of early December 2024, and later reporting suggests a landing page still existed. - #12[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Reporting
“ZachXBT, the pseudonymous on-chain investigator, is cited by AVOID.NET as having flagged Sunray Finance.”
reviewerZachXBT flagged Sunray FinanceThe page itself concedes that no ZachXBT post was found. Neither cited source mentions him.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #5[partially supported][awaiting moderator]in section: Attack Mechanism and Root Cause
“The Sunray Finance team publicly stated that the private key was compromised and denied insider involvement, though this claim has not been independently verified.”
reviewerTeam attributed the exploit to a compromised private key and denied insider involvementKey-compromise attribution is hedged in Quadriga, but the denial of insider involvement is not found in any readable source. The Olympix article could not be fetched. - #8[partially supported][awaiting moderator]in section: Pre-Exploit Red Flags and Marketing Claims
“The team did not issue any public notifications of the exploit through their official channels — neither Sunray Finance nor Sunray Swap announced the hack through their social media or communications at the time it occurred.”
reviewerTeam issued no public notification of the exploit through official channelsSunray did post on X on Oct 30 (a statement about treasury tokens moving, without calling it a hack), which conflicts with this sentence and with sections[4]. The page contradicts itself. Suggest narrowing to 'did not describe the incident as a hack'. - #14[partially supported][awaiting moderator]in section: Regulatory and Legal Status
“As of available reporting through mid-2025, the Sunray Finance website (sunray.finance) is offline.”
reviewerWebsite is offline and the SUN token is effectively worthless as of mid-2025The offline status is documented only as of Dec 2024. The 'mid-2025' date is not backed by a fetched source, and the live state of the domain was not independently checked.
confirmed
8 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Exploit Overview
“On October 30, 2024, an attacker exploited Sunray Finance's upgradeable contract architecture on the Arbitrum network.”
reviewerExploit occurred October 30, 2024 on Arbitrum, with the attacker upgrading the management contract and minting about 200 sextillion SUN tokensDate, chain and mechanism match multiple outlets. Quadriga mentions an Oct 29 upgrade in one passage, a minor discrepancy. - #2[confirmed][no action needed]in section: Exploit Overview
“The attacker then swapped half of these tokens through DEX liquidity pools for approximately $2.1 million worth of Tether (USDT).”
reviewerAttacker swapped half the minted tokens for about $2.1 million USDTSupported by Cointelegraph, Web3 Is Going Great and Quadriga. - #3[confirmed][no action needed]in section: Exploit Overview
“The attacker's initial wallet was funded via the Across bridge from Ethereum, indicating pre-planned operational steps.”
reviewerAttacker's initial wallet was funded via Across bridge from EthereumFunding fact supported; the inference of pre-planning is interpretive. - #6[confirmed][no action needed]in section: Secondary Arbitrage Event
“The arbitrage bot operator realized a profit of approximately $560,000 worth of Ether (ETH).”
reviewerArbitrage bot realized about $560,000 in ETH from a second liquidity pool the attacker missedThe specific '90 sextillion' figure was not found in the fetched sources. - #7[confirmed][no action needed]in section: Pre-Exploit Red Flags and Marketing Claims
“First, the project claimed backing from Japanese investment giant SoftBank; however, SoftBank's official portfolio page did not list Sunray Finance, and SoftBank has not publicly acknowledged any relationship with the project.”
reviewerSoftBank backing was claimed but SoftBank's portfolio does not list the projectMatches both sources. The claim is framed as unverified, consistent with the sources. - #9[confirmed][no action needed]in section: Pre-Exploit Red Flags and Marketing Claims
“Third, the SUN token launched around September 17, 2024, and grew from approximately $7 to $10 in value before the exploit approximately six weeks later.”
reviewerSUN launched about Sept 17, 2024 at about $7 and rose to about $10 before the exploitSupported. Sept 17 to Oct 30 is about six weeks. - #10[confirmed][no action needed]in section: Team Response and Recovery Efforts
“The team also reported contacting Binance and Binance's security team to assist with potential recovery efforts.”
reviewerTeam contacted Binance security for recovery assistanceSupported by Quadriga only, which is a single tier-3 source. - #13[confirmed][no action needed]in section: Regulatory and Legal Status
“No regulatory actions by the SEC, CFTC, DOJ, or any other governmental authority against Sunray Finance or its team members have been identified in publicly available records as of the time of this investigation.”
reviewerNo regulatory or criminal action has been identifiedA negative claim, phrased as 'not identified'. My search also found nothing contrary.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.