Skip to main content
AVOID.NET

Fact-check findings

What an automated fact-checker found when it re-read Namada Protocol — MASP IBC Transfer Logic Exploit (June 19 2026) 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

1 claim

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
    “2026-06-21”
    reviewerNamada's team publicly confirmed the exploit on 2026-06-21Two independent reports date Namada's statement to June 20, not June 21. June 21 is not supported.
    Proposed correction (not yet applied)
    2026-06-20

unverifiable

3 claims

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

  1. #4[unverifiable][awaiting moderator]in the summary
    “the discrepancy was first identified by independent security researchers at F12”
    reviewerF12 identified the drain; stale indexer masked itCryptoTimes returned 403. Other outlets do not mention F12 and attribute the detection to Odaily on-chain tracking.
  2. #6[unverifiable][awaiting moderator]in the timeline
    “2024-12-03”
    reviewerNamada mainnet launched December 3, 2024Not fetched in this pass; background claim is outside the incident. The page's other background claims (CHF 100,000 bounty, 180 validators, April 2024 rollout) were also not checked.
  3. #7[unverifiable][awaiting moderator]in section: Incident Overview
    “This is the first publicly disclosed exploit of Namada's shielded pool infrastructure since the protocol's mainnet launched on December 3, 2024.”
    reviewerFirst publicly disclosed exploit of Namada's shielded pool since mainnet launchA universal negative with no cited source. Searches surfaced no earlier disclosed MASP exploit, but that is not proof.

partially supported

2 claims

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

  1. #2[partially supported][awaiting moderator]in the timeline
    “2026-06-19”
    reviewerThe ATOM transfer to the cosmos1zw9... address happened on June 19The page's own timeline already lists June 18 as the start of the drain, and KuCoin/Odaily gives June 18 for the ATOM receipt. The June 19 headline date in the title, summary and slug may be wrong. The primary CryptoTimes source could not be read. Only the timeline field is proposed as an edit, because the date in the title and summary rests on an unreadable source.
  2. #3[partially supported][awaiting moderator]in the summary
    “drained of approximately $600,000 in IBC-bridged assets including ATOM, USDC, OSMO, TIA, and NYM”
    reviewerApproximately $600,000 drained from Namada MASP in ATOM, USDC, OSMO, TIA, NYMThe $600K loss is corroborated. The asset breakdown is only in the unreadable CryptoTimes article.

confirmed

1 claim

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: Namada's Response and Investigation Status
    “'There's been an exploit in the Namada protocol. We are investigating the issue and are involving the relevant parties.'”
    reviewerNamada's quoted statements and appeal to a white hatThe quotes match CoinTrust. It also reports the team working with validators and security partners.
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.