Skip to main content
AVOID.NET
← SUNRAY·FINANCE5 decisions on this page

Audit log

Every state-changing event for SUNRAY·FINANCE: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-28 02:26:57Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 422,629,060
    sig
    2fMXjResmJFh…LsQCWB5Xexplorer ↗
    hash
    DYYmz6nb7dkd…KsE9Dz57sha256 → base58
    verifying row…full verify ↗
    canonical bytes (5900 B) ▸
    {"actor":"system:backfill","investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","kind":"publish","page_slug":"sunrayfinance","published_at":"2026-05-28T02:26:57.505Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"SUNRAY·FINANCE","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/btc-scammers-sunray-finance-crypto-sec","type":"other","url":""},{"credibility":3,"name":"https://www.cryptopolitan.com/malicious-smart-contract-causes-2-8m-in-sun-token-losses-on-arbitrum/","type":"other","url":""},{"credibility":3,"name":"https://olympixai.medium.com/sunray-finance-fire-token-and-onyxdao-drained-via-key-compromise-launch-time-burn-flaw-and-4a062046957d","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/sunray-finance-hack","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://smartcontractshacking.com/hacks/sunray-finance-hack-2024","type":"other","url":""},{"credibility":3,"name":"https://olympixai.medium.com/sunray-finance-fire-token-and-onyxdao-drained-via-key-compromise-launch-time-burn-flaw-and-4a062046957d","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/9ce1e-malicious-smart-contract-causes-2-8m-in-sun-token-losses-on-arbitrum","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/sunray-finance-hack","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/btc-scammers-sunray-finance-crypto-sec","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cryptorank.io/news/feed/9ce1e-malicious-smart-contract-causes-2-8m-in-sun-token-losses-on-arbitrum","type":"other","url":""},{"credibility":3,"name":"https://www.cryptopolitan.com/malicious-smart-contract-causes-2-8m-in-sun-token-losses-on-arbitrum/","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""},{"credibility":3,"name":"https://olympixai.medium.com/sunray-finance-fire-token-and-onyxdao-drained-via-key-compromise-launch-time-burn-flaw-and-4a062046957d","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/9ce1e-malicious-smart-contract-causes-2-8m-in-sun-token-losses-on-arbitrum","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/btc-scammers-sunray-finance-crypto-sec","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/sunray-finance-hack","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/sunrayfinancemaliciousupgradeandtokenminting.php","type":"other","url":""},{"credibility":3,"name":"https://smartcontractshacking.com/hacks/sunray-finance-hack-2024","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/sunray-finance-hack","type":"other","url":""}]}],"sources_used":[],"summary":"Sunray Finance was a perpetual-trading DEX protocol on Arbitrum that suffered a critical exploit on October 30, 2024, resulting in approximately $2.7–2.9 million in losses. An attacker — using what the team attributed to a compromised private key — upgraded the protocol's management contract and minted 200 sextillion SUN tokens, then swapped a portion for USDT before the token price collapsed to zero. The project website subsequently went offline with no confirmed fund recovery, and the protocol's pre-exploit marketing included unverified claims of SoftBank backing and unsustainable 299% annual yield promises.","timeline":[{"date":"2024-09-17","event":"SUN token launches on Arbitrum at approximately $7, with trading beginning on the Sunray Finance DEX.","source":""},{"date":"2024-10-01","event":"SUN token price reaches approximately $10 as the protocol markets 299% annual yield and alleged SoftBank backing.","source":""},{"date":"2024-10-30","event":"Attacker upgrades Sunray Finance management contract (0xb1bbe57f5c474996a84274f0078a2411e1a65b8a) and mints 200 sextillion SUN tokens, swapping approximately half for $2.1 million USDT. SUN token price collapses to zero. Separate arbitrage bot captures ~$560,000 ETH profit from a secondary liquidity pool.","source":""},{"date":"2024-10-31","event":"CoinTelegraph, Cryptopolitan, and other outlets report the exploit. Total losses confirmed at approximately $2.7–2.9 million. Sunray Finance team posts on social media claiming private key compromise and denying insider involvement.","source":""},{"date":"2024-11-01","event":"Sunray Finance team reports contacting Binance security team for recovery assistance. No further updates issued to the public afterward.","source":""},{"date":"2024-11-30","event":"Sunray Finance website goes offline. No recovery or user reimbursement announced.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision e20acbfb-765d-4af2-861c-905f802ddb95
  2. #2rescoreby systemsystem
    2026-10-10 18:41:29Z
    Score: 8 → 44 (+36)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 8 → 44. Problems weighed by who is responsible: incidents the subject suffered −9.6, the subject's own conduct −8, problems around the subject, caused by others −3.2.
    anchoranchored
    chain
    ●mainnet-betaslot 455,360,507
    sig
    2EJXzjpXnoSe…RNxfsK8Nexplorer ↗
    hash
    ANtsBZRzwViT…S2baoPYAsha256 → base58
    verifying row…full verify ↗
    canonical bytes (603 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:41:29.747Z","decision":"rescore","investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","new_score":44,"page_slug":"sunrayfinance","prev_score":8,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 8 → 44. Problems weighed by who is responsible: incidents the subject suffered −9.6, the subject's own conduct −8, problems around the subject, caused by others −3.2.","score_delta":36,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 3802df80-bda7-4005-a4b8-3e4c79519440
  3. #3reviewby reviewerreviewer
    2026-11-02 03:44:35Z
    Score: 44 → 44 (no score change)
    The core exploit facts (Oct 30, 2024 date, contract upgrade, 200 sextillion SUN minted, about $2.1M USDT swapped, about $560K bot profit, loss range of $2.7-2.9M, SoftBank and 299% claims) are supported by Cointelegraph, Cryptopolitan, Web3 Is Going Great and Quadriga. Weaker points are the timeline date for the website going offline (2024-11-30, with no source), the 'denied insider involvement' claim, the unverified contract address, and a sentence saying the team made no announcement when it did post on X. The page leans on Quadriga for the aftermath, and the Olympix source was unreadable.
    anchoranchored
    chain
    ●mainnet-betaslot 464,348,643
    sig
    5YFdxFeje8az…HY7BCBkGexplorer ↗
    hash
    8vbbLTtcgSzQ…1KuoVkKhsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1451 B) ▸
    {"actor":"reviewer","artifact_identity":"3cdbe0482538b32a517ca562190fb3fa","decided_at":"2026-11-02T03:44:35.085Z","decision":"review","disputed_pct":0.2143,"findings_hash":"56NBWisy1SjevpywLg6pUoxXrpPqWozhctjstTPwJNnq","investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":44,"omissions":{"material":0,"total":1},"page_content_hash":"ab34d9eac49ebc7c10fcfee1b1ca03ecfff3f26129465406b3e8ffb49164744d","page_slug":"sunrayfinance","prev_score":44,"reason":"The core exploit facts (Oct 30, 2024 date, contract upgrade, 200 sextillion SUN minted, about $2.1M USDT swapped, about $560K bot profit, loss range of $2.7-2.9M, SoftBank and 299% claims) are supported by Cointelegraph, Cryptopolitan, Web3 Is Going Great and Quadriga. Weaker points are the timeline date for the website going offline (2024-11-30, with no source), the 'denied insider involvement' claim, the unverified contract address, and a sentence saying the team made no announcement when it did post on X. The page leans on Quadriga for the aftermath, and the Olympix source was unreadable.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision aa43126b-6351-416b-abd5-f4b5f80dc7a1
  4. #4review reviseby judgejudge
    2026-11-02 03:44:35Z
    Score: 44 → 44 (no score change)
    The core exploit facts (October 30, 2024 date, contract upgrade, SUN minting, about $2.1M USDT swapped, about $560K bot profit) were confirmed by several outlets (claim_findings[0], [1], [5]). Three of 14 claims (21%) could not be verified: the exploited contract address (claim_findings[3]), the exact 2024-11-30 website-offline date (claim_findings[10]) and the ZachXBT flag (claim_findings[11]). Other claims are only partly supported: the 'no public notification' sentence conflicts with an October 30 X post and with the page's own team-response section (claim_findings[7]), and the 'denied insider involvement' and 'mid-2025 offline' statements lack backing (claim_findings[4], [12]). The reviewer flagged a high-priority gap in on-chain verification, which fits a minor-issues revision rather than approval.
    anchoranchored
    chain
    ●mainnet-betaslot 464,348,648
    sig
    3vT4LNcHg3Lm…eEVkTa72explorer ↗
    hash
    9ScuLWAbFw4v…xNHVEdLjsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1461 B) ▸
    {"actor":"judge","artifact_identity":"3cdbe0482538b32a517ca562190fb3fa","band_override":null,"decided_at":"2026-11-02T03:44:35.085Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2143,"investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":44,"page_slug":"sunrayfinance","prev_score":44,"reason":"The core exploit facts (October 30, 2024 date, contract upgrade, SUN minting, about $2.1M USDT swapped, about $560K bot profit) were confirmed by several outlets (claim_findings[0], [1], [5]). Three of 14 claims (21%) could not be verified: the exploited contract address (claim_findings[3]), the exact 2024-11-30 website-offline date (claim_findings[10]) and the ZachXBT flag (claim_findings[11]). Other claims are only partly supported: the 'no public notification' sentence conflicts with an October 30 X post and with the page's own team-response section (claim_findings[7]), and the 'denied insider involvement' and 'mid-2025 offline' statements lack backing (claim_findings[4], [12]). The reviewer flagged a high-priority gap in on-chain verification, which fits a minor-issues revision rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision d9ded593-a014-498f-9c79-3c7a6a296cb4
  5. #5rescoreby systemsystem
    2026-11-02 03:44:36Z
    Score: 44 → 45 (+1)
    Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 44 → 45. Problems weighed by who is responsible: incidents the subject suffered −9.6, the subject's own conduct −8, problems around the subject, caused by others −2.4; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 464,348,653
    sig
    2TDhXBvmYSHW…46e8CbKXexplorer ↗
    hash
    FfWQSd3ey9Bw…eaSyaiAKsha256 → base58
    verifying row…full verify ↗
    canonical bytes (715 B) ▸
    {"actor":"system","decided_at":"2026-11-02T03:44:35.085Z","decision":"rescore","investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","new_score":45,"page_slug":"sunrayfinance","prev_score":44,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 44 → 45. Problems weighed by who is responsible: incidents the subject suffered −9.6, the subject's own conduct −8, problems around the subject, caused by others −2.4; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 5373d15b-9124-4bfa-95e2-1c23bdfd4fd2
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.