Skip to main content
AVOID.NET
← Moby Tradereviewed 2026-11-02 · 13 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Moby Trade 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.

disputed

4 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in section: Security Incident — January 2025 Private Key Compromise
    “extracting 207.78 wETH (approximately $627,678), 3.774 wBTC (approximately $345,222), and 30,180 USDC from the vaults, totalling approximately $2.47 million.”
    reviewerExtracted vault amounts (207.78 wETH, 3.774 wBTC, 30,180 USDC) total approximately $2.47 millionThe listed figures sum to about $1.003M, not $2.47M. The page leaves out the ~1.47M USDC that made up the rest of the gross theft, so the sentence is internally inconsistent.
    Proposed correction (not yet applied)
    extracting 207.78 wETH (approximately $627,678), 3.774 wBTC (approximately $345,222), and 30,180 USDC from the vaults, totalling approximately $1.0 million, in addition to approximately 1.47 million USDC that was later recovered, for a gross loss of approximately $2.5 million.
  2. #4[disputed][awaiting moderator]in section: Fund Laundering and On-Chain Tracing
    “the unrecovered ETH and WBTC were dispersed across more than 35 wallet addresses in an apparent effort to obfuscate the trail.”
    reviewerFunds dispersed across more than 35 wallet addressesThe cited source says more than ten, not 35. The 35+ figure also appears in timeline[5].
    Proposed correction (not yet applied)
    the unrecovered ETH and WBTC were dispersed across more than ten wallet addresses in an apparent effort to obfuscate the trail.
  3. #5[disputed][awaiting moderator]in the timeline
    “Remaining stolen ETH and WBTC begin dispersal across 35+ wallet addresses; 9.5634 ETH routed through Railgun privacy protocol.”
    reviewerTimeline entry repeats the 35+ wallets figureSame wallet-count error as sections[1]. The Railgun amount is correct.
    Proposed correction (not yet applied)
    Remaining stolen ETH and WBTC begin dispersal across more than ten wallet addresses; 9.5634 ETH routed through Railgun privacy protocol.
  4. #8[disputed][awaiting moderator]in the summary
    “the unrecovered ~$1 million in ETH and WBTC was routed through privacy mixers including Railgun and Tornado Cash”
    reviewerStolen funds were routed through Tornado Cash (summary)Summary overstates. Tornado Cash is a prior link, and Railgun received about 9.56 ETH, not the bulk of the ~$1M. The summary also claims 'effectively unrecoverable', which is the page's inference.
    Proposed correction (not yet applied)
    the unrecovered ~$1 million in ETH and WBTC was dispersed across multiple addresses, with a portion (9.5634 ETH) routed through Railgun; the attacker's funding address had earlier received a Tornado Cash withdrawal (September 2024)

unverifiable

4 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #3[unverifiable][awaiting moderator]in section: Security Incident — January 2025 Private Key Compromise
    “The attacker first tested the exploit on Arbitrum Sepolia testnet at approximately 11:56 UTC, then executed a malicious contract upgrade on mainnet at 12:53 UTC, transferring admin privileges to an attacker-controlled address.”
    reviewerAttack timestamps (Sepolia test 11:56 UTC, upgrade 12:53 UTC, drain 15:24-16:48 UTC)Primary post-mortem was blocked, and the other cited sources give no times. The claim is neither supported nor contradicted.
  2. #10[unverifiable][awaiting moderator]in section: Team Response and Compensation
    “Protocol operations resumed on a target date of January 15, 2025 with new security measures in place.”
    reviewerCompensation by Jan 13, resumption Jan 15, 2025, and measures taken; Circle, Stargate, Rhino.fi coordinationDates and security-measure details rest on the blocked Medium post-mortem. Only the general compensation promise was corroborated. The page also says 'Protocol operations resumed' as if completed, though the section frames it as a target date. The timeline[8] entry states it as fact.
  3. #11[unverifiable][awaiting moderator]in the timeline
    “Moby Trade publishes incident report; users urged to revoke token approvals. Protocol operations suspended.”
    reviewerTimeline: Jan 10 incident report published and protocol operations suspendedCould not read the post-mortem to confirm the Jan 10 date. Rekt (published Jan 13) and Halborn (Jan 14) do not state it.
  4. #13[unverifiable][awaiting moderator]in section: Regulatory and Compliance Status
    “No regulatory actions by the SEC, CFTC, DOJ, or any other government body against Moby Trade have been identified as of the research date.”
    reviewerNo regulatory actions identified against MobyNo contrary reports found, but the cited source does not address regulation. A negative claim is not provable from it.

partially supported

3 claims

The cited evidence supports part of the claim but not all of it.

  1. #2[partially supported][awaiting moderator]in section: Security Incident — January 2025 Private Key Compromise
    “MEV researcher Tony Ke (Solayer Labs/Fuzzland) exploited this oversight to recover 1,470,191 USDC before the attacker could move it, finishing approximately 30 seconds behind the original attacker in doing so.”
    reviewerTony Ke is affiliated with Solayer Labs/Fuzzland and acted as an MEV researcherRecovery, the 1.47M USDC figure and the 30-second gap are supported. The Solayer/Fuzzland affiliation is not in any fetched source. The sources describe the 30-second miss as applying to the remaining funds, not to the USDC that was recovered.
  2. #7[partially supported][awaiting moderator]in section: Fund Laundering and On-Chain Tracing
    “Recovered USDC was deposited to OKX exchange.”
    reviewerRecovered USDC was deposited to OKX exchangeDirectionally supported, but the page leaves the recovery mechanism unclear. Merkle's flow description conflicts somewhat with the SEAL911 counter-exploit narrative in Rekt and Halborn. Reviewer could not fully reconcile them.
  3. #12[partially supported][awaiting moderator]in section: Protocol Background and History
    “The protocol received an Arbitrum Foundation grant in January 2024, becoming the first options protocol to receive such a grant prior to mainnet launch.”
    reviewerArbitrum Foundation grant in January 2024 and mainnet launch April 2024Dates fit self-issued press releases and search snippets. 'First options protocol' is a self-promotional claim, not independently verified. Cited PR Newswire pages were not fetched individually.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #6[confirmed][no action needed]in section: Fund Laundering and On-Chain Tracing
    “a prior connection was identified between the attacker's funding address and a Tornado Cash withdrawal of 0.9706 ETH dating to September 27, 2024”
    reviewerTornado Cash withdrawal of 0.9706 ETH on 2024-09-27 by the attacker's funding addressSupported. The 'premeditation' inference elsewhere is the page's own interpretation.
  2. #9[confirmed][no action needed]in section: Protocol Background and History
    “In February 2025, Moby expanded to the Berachain mainnet, integrating with Berachain's Proof of Liquidity consensus mechanism through a Structured Product Vault, and was selected for Berachain's Request for Application program.”
    reviewerBerachain expansion in Feb 2025, RFA selection, partners, $3.5B volumeSupported by the project's own press release (self-reported). The $3.5B volume and 'leading' claims are project marketing.
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.