Skip to main content
AVOID.NET
← Base Chain Vault Hack (October 2026)reviewed 2026-10-27 · 11 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Base Chain Vault Hack (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 4confirmed 60 corrections pending · 0 applied

unverifiable

1 claim

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

  1. #3[unverifiable][awaiting moderator]in section: The Exploit
    “the vault's multisig removed a newly deployed contract from its own asset whitelist, then re-added (re-enabled) that same contract roughly one minute later at 08:53 UTC”
    reviewerWhitelist removal at 08:52 UTC, re-enable at 08:53 UTC, first borrow ~09:04 UTC, valid ECDSA signature recoveries matching existing signersTiming of two changes is corroborated. The remove/re-add framing, the 09:04 UTC borrow time and the ECDSA statement could not be verified because the cited source was blocked.

partially supported

4 claims

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

  1. #5[partially supported][awaiting moderator]in section: Escalating Loss Estimate During Live Incident
    “The rapid upward revision reflects the fact that the attack involved multiple sequential outflows (six documented withdrawals) rather than a single transaction, and that loss trackers updated their totals as each subsequent withdrawal was identified on-chain while the incident was still unfolding.”
    reviewerLoss revision was caused by six documented withdrawals and trackers updating as each was identifiedSix outflows is supported. The causal explanation of the estimate revision is the page's inference, not stated by the sources.
  2. #9[partially supported][awaiting moderator]in the timeline
    “2026-10”
    reviewerTimeline: multisig re-adds contract; date stored only as month although the day is knownThe date is imprecise rather than wrong. The day is established as 2026-10-04.
  3. #10[partially supported][awaiting moderator]in the timeline
    “2026-10”
    reviewerTimeline: first borrow; date stored only as monthImprecise date; the incident day is October 4.
  4. #11[partially supported][awaiting moderator]in the timeline
    “2026-10”
    reviewerTimeline: PeckShield confirms 1,783 wstETH; date stored only as monthPeckShield figure confirmed. The 09:56 UTC time is not checkable because the CryptoTimes page was blocked.

confirmed

6 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: The Exploit
    “pulling out 1,783.067 aBaswstETH”
    reviewerAbout 1,783 wstETH (~$6M) was drained; 1,783.067 aBaswstETH borrowed and redeemed via AaveAmount and mechanism match the fetched article.
  2. #2[confirmed][no action needed]in section: The Exploit
    “The destination attacker address has been identified on-chain as 0x0B5126e1bc27C0de77e02e97945760A674EdB034”
    reviewerAttacker address and vault proxy addressBoth addresses match independent articles. The cited CryptoTimes page returned 403.
  3. #4[confirmed][no action needed]in section: Escalating Loss Estimate During Live Incident
    “The security monitoring firm Blockaid first flagged the exploit publicly at approximately 09:20–09:21 UTC on October 4, 2026, when the loss was initially estimated at roughly $2.02 million.”
    reviewerBlockaid flagged the exploit at ~09:21 UTC with an initial estimate of ~$2.02M; losses exceeded $6M ~40 minutes laterMatches the source.
  4. #6[confirmed][no action needed]in section: Undisclosed 3-of-7 Multisig Governance
    “requiring 3 of 7 signatures to execute transactions, deployed via Safe Proxy Factory version 1.4.1 and created approximately 324 days before the incident”
    reviewerSafe at 0x6b27... is 3-of-7, Safe Proxy Factory 1.4.1, created ~324 days earlier, signers unidentified, no one claimed the vaultMatches. Note the source calls the Safe an owner of the vault; the page's phrase 'governed by' is a fair paraphrase.
  5. #7[confirmed][no action needed]in section: Undisclosed 3-of-7 Multisig Governance
    “no entity had issued an official post-mortem or statement about the incident”
    reviewerNo official post-mortem issued and no entity claimed the vaultA search found nothing newer than early-October coverage.
  6. #8[confirmed][no action needed]in section: Scope: Base and Aave Infrastructure Not Compromised
    “Analysis from Spot On Chain noted that systemic risk to the broader market was assessed as limited, though it flagged short-term concern that the attacker selling the stolen wstETH could place downward pressure on the liquid staking token's peg to ETH.”
    reviewerBase and Aave core infrastructure not compromised; Spot On Chain noted limited systemic risk and possible wstETH peg pressureMatches PANews.
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.