Skip to main content
AVOID.NET

Fact-check findings

What an automated fact-checker found when it re-read MetaMask Infrastructure Security Incident (October 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.

unverifiable 1partially supported 5confirmed 20 corrections pending · 0 applied

unverifiable

1 claim

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

  1. #6[unverifiable][awaiting moderator]in section: Wallet and User Fund Safety
    “The RLUSD vault reportedly fell from approximately $426 million to $350 million and the PYUSD vault from approximately $409 million to $349 million within a four-hour window.”
    reviewerSentora vault outflows within a four-hour window with specific vault sizesThe $1.1B AUM and the not-technically-exposed caveat are supported. The before/after figures and four-hour window are not in the cited article. CoinDesk mentions Ethena withdrawing about $75M and $60M from RLUSD and PYUSD vaults, which does not match the page's drops of about $76M and $60M exactly. I did not find a source for the page's numbers. Also, 'second-largest' is consistent with 'behind Steakhouse Financial'.

partially supported

5 claims

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

  1. #2[partially supported][awaiting moderator]in section: Nature of the Compromise: Fee Recipient Redirection
    “Kaden's analysis concluded that the attacker does not appear to have been capable of extracting the staked principal, and that three validators were suspected of confirmed compromise with 821 additional validators flagged as potentially affected.”
    reviewerKaden reported 18 of 19 validators sent rewards to a Tornado Cash-funded address, about 0.36 ETH, 3 suspected and 821 potentially affected validatorsCore figures are supported, but only by secondary aggregators, not a primary Kaden source. The wording 'suspected of confirmed compromise' is self-contradictory. The page does disclose that MetaMask has not confirmed the findings.
  2. #3[partially supported][awaiting moderator]in section: Nature of the Compromise: Fee Recipient Redirection
    “The total value diverted was approximately 0.36 ETH, worth roughly $966 at ETH prices near $2,684 at the time of reporting.”
    reviewerDiverted value was roughly $966 at ETH near $2,684The dollar figure is arithmetically consistent (0.36 x 2684 is about 966) but I did not find it in the cited page. The CoinPaprika headline says sub-$1,000. I did not fetch CoinPaprika.
  3. #4[partially supported][awaiting moderator]in section: Scale of the Validator Exit and Operational Impact
    “These validators collectively held roughly 523,000 ETH, valued at approximately $1.4 billion at prevailing prices.”
    reviewerAbout 17,000 validators holding roughly 523,000 ETH (around $1.4 billion) being exitedValidator and ETH counts are supported, but CoinDesk labels them an unconfirmed researcher estimate. The page attributes them to 'independent on-chain analysis'. The $1.4B figure is not in CoinDesk (523,000 x about $2,684 is about $1.40B, so it is consistent). The summary states these figures flatly, with no 'reportedly'.
  4. #5[partially supported][awaiting moderator]in section: Scale of the Validator Exit and Operational Impact
    “Lido confirmed that validator exits had begun and were expected to complete by October 7, 2026.”
    reviewerLido expects exits complete by Oct 7 and reentry could take about 45 daysConfirmed as of Oct 1 but now stale in framing. The Oct 7 date is long past (today is 2026-10-27) and the page still treats it as forthcoming. The page also says 'complete' where Lido said validators stop staking, not that funds are withdrawn.
  5. #7[partially supported][awaiting moderator]in the timeline
    “The Ethereum validator withdrawal queue reaches approximately 773,447 ETH — the largest since December 2025 — with an estimated wait time of 13 days and 10 hours.”
    reviewerWithdrawal queue about 773,447 ETH, largest since December 2025The queue peaked higher than the page's figure on Oct 2. The page's wording is a snapshot, which is acceptable but incomplete. This was not directly verified against the cited page.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Incident Overview
    “A follow-up update on October 1, 2026 stated: 'there is no indication that MetaMask wallets or customer funds have been affected.'”
    reviewerMetaMask first notice Sept 30 and Oct 1 follow-up wordingOfficial statements match. The cited metamask.io URL now 301-redirects to metamask.com, which still serves the content.
  2. #8[confirmed][no action needed]in section: Downstream DeFi Contagion: Sentora Morpho Vault Outflows
    “As of October 4, 2026 (the investigation date), no post-incident technical disclosure, post-mortem, or root-cause analysis has been published by MetaMask or ConsenSys.”
    reviewerNo post-incident disclosure as of Oct 4, 2026Holds as dated. The official page shows dateModified Oct 8 with no content after Oct 1. The page is about three weeks old as of today and should be re-checked.
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.