Skip to main content
AVOID.NET
← Poly Networkreviewed 2026-11-01 · 10 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Poly Network 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

2 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 the timeline
    “August 15: Tether Ltd. confirms it froze $33.4 million in USDT linked to the attacker's wallet immediately after the hack.”
    reviewerTether confirmed on August 15, 2021 that it froze $33.4 million in USDT immediately after the hackThe freeze was reported on August 10, 2021, not August 15, and the frozen USDT was later released to Poly Network. The entry has no source. I did not fetch the primary Tether or Ardoino post, so this rests on search snippets.
    Proposed correction (not yet applied)
    August 10: Tether CTO Paolo Ardoino announces Tether has frozen about $33 million in USDT linked to the attacker's wallet; Tether released the frozen funds (about $33.4 million) to Poly Network on August 25.
  2. #6[disputed][awaiting moderator]in section: Regulatory and law enforcement context
    “two major security incidents within about two years (the August 2021 exploit of roughly $610–611 million and the July 2023 exploit with realised losses estimated at $5–20 million)”
    reviewerServices were permanently shut down; the page presents the 2021 and 2023 incidents as the only security incidents ('two major security incidents within about two years')A third exploit in August 2024, about six weeks before the shutdown, is missing from the page. The wording 'two ... incidents' is therefore inaccurate. The correction wording is drawn from secondary Neo News Today and Cryptonews coverage, and the loss figure varies ($3M to $5M) by source.
    Proposed correction (not yet applied)
    three security incidents (the August 2021 exploit of roughly $610–611 million, the July 2023 exploit with realised losses estimated at $5–20 million, and an August 2024 exploit of the cross-chain manager contract with losses reported at about $3–5 million)

unverifiable

3 claims

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

  1. #3[unverifiable][awaiting moderator]in section: July 2023 exploit and keeper key compromise
    “noted: 'Poly Network had a simple 3 of 4 multisig arrangement over 2 years — which is incredibly risky.'”
    reviewerDedaub quote about a 3-of-4 multisig operated for 2 yearsThe substance (3 of 4 keys, unchanged for 2 years) is supported. The exact quotation could not be located, and the fetch was summarised, so it may exist in the full text. Dedaub described the cause as 'likely', which is more hedged than the page's 'concluded'.
  2. #7[unverifiable][awaiting moderator]in section: Risk flags and community concerns
    “Blockchain investigator ZachXBT has reportedly listed Poly Network among exploited or risky crypto entities following its repeated breaches.”
    reviewerZachXBT has listed Poly Network among exploited or risky entitiesNo source was cited and I found none. 'Reportedly' with no reference is a weak attribution to a named individual, and the claim should be removed unless sourced. The same applies to the unsourced Reddit and Crypto Twitter criticism.
  3. #10[unverifiable][awaiting moderator]in section: July 2023 exploit and keeper key compromise
    “Reports differ on the scope: 57 assets on 10 blockchains (including Ethereum, BNB Chain, Polygon, Avalanche, Metis and Optimism) according to the survivor page's sources, and 58 assets on 11 blockchains according to the merged page's sources.”
    reviewerJuly 2023 exploit details, scope and loss estimatesI did not verify the 57/10 versus 58/11 figures. The broad loss range of $5-20M is consistent with search coverage (Benzinga and others cite over $10M). The internal merge language should be rewritten.

partially supported

2 claims

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

  1. #2[partially supported][awaiting moderator]in section: 2021 fund return and the 'Mr. White Hat' framing
    “the survivor page states that everything was returned except $33.4 million in USDT that Tether Ltd. froze immediately after the hack, while the merged page states that Poly Network confirmed all assets recovered.”
    reviewerRecovery was complete except for $33.4M USDT that Tether frozeThe two accounts are not really in conflict. Tether released the frozen USDT to Poly Network around Aug 25, so recovery was effectively complete. The editorial wording about 'survivor page' and 'merged page' is internal merge language that should not appear in a published page.
  2. #4[partially supported][awaiting moderator]in the timeline
    “July 3: Dedaub publishes a post-mortem attributing the attack to compromised keeper private keys rather than a smart contract bug.”
    reviewerDedaub published its post-mortem on July 3, 2023The attribution is supported, but the exact date is unconfirmed because the page's own date metadata is unreliable.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in the timeline
    “September 11: Poly Network announces complete termination of all services effective September 30, 2024, citing the 'changing market landscape'.”
    reviewerPoly Network published termination notice on Sept 11, 2024 effective Sept 30, 2024, citing changing market landscapeThe primary notice returned 403. The secondary coverage published a day after the claimed notice date is consistent with it. The page's own wording says 'changing market landscape' while the secondary source says 'changing market conditions'; this is minor.
  2. #8[confirmed][no action needed]in section: 2021 fund return and the 'Mr. White Hat' framing
    “By August 13 approximately $340 million had been returned, with remaining assets moved to a multi-signature address requiring Poly Network's cooperation for transfer.”
    reviewerMr. White Hat, 500k bounty, chief security advisor, 340M returned by Aug 13, final tranche Aug 25The Wikipedia article matches the page.
  3. #9[confirmed][no action needed]in section: August 2021 exploit
    “On August 10, 2021, an unknown attacker exploited a critical access control vulnerability in Poly Network's smart contracts, taking roughly $610–611 million in cryptocurrency, the largest DeFi hack recorded at that time.”
    reviewerAugust 10, 2021 exploit of roughly $610 million with per-chain splitThe core facts hold. The per-chain split was not independently checked. The prose in this section contains internal merge artefacts ('survivor page', 'merged page') that should be removed.
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.