Fact-check findings
What an automated fact-checker found when it re-read Volo Vault against the sources the page cites. Only the most recent review is shown.
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
5 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #3[unverifiable][awaiting moderator]in section: Security Exploit — April 2026
“This incident was flagged by on-chain investigator ZachXBT.”
reviewerZachXBT flagged the incidentVolo reportedly engaged ZachXBT after disclosure (per the timeline), but I found no source saying he flagged the incident. Not checked in the other cited sources. - #6[unverifiable][awaiting moderator]in section: Admin Key and Centralization Risk
“The post-mortem had not been published as of the date of this investigation.”
reviewerPost-mortem not yet published / compensation mechanism pending as of investigationPage is dated about May 2026 and the review is in November. Later recovery updates exist, so this may be out of date. Could not confirm either way. - #7[unverifiable][awaiting moderator]in the timeline
“Veridise completes formal audit of NAVI-Volo Vault v3 smart contracts (VAR-NAVI-250523-SUI-VOLO-VAULT-V3).”
reviewerVeridise audit completed November 2025I did not fetch the PDF. The report ID suggests a May 2025 engagement and only the upload path says 2025/11, so the audit date is uncertain. - #9[unverifiable][awaiting moderator]in section: Corporate History and NAVI Acquisition
“No specific founders or individual team members have been publicly identified in available sources.”
reviewerNo founders or team members publicly identifiedA negative claim I did not test. - #10[unverifiable][awaiting moderator]in section: Regulatory Status
“No SEC, CFTC, DOJ, or other regulatory enforcement actions against Volo Protocol or Volo Vault have been identified in publicly available records as of May 2026.”
reviewerRegulatory status: no enforcement, no OFAC listingAbsence claim with no sources. My status search found no enforcement action.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Recovery and Compensation
“By April 27, 2026, Volo reported that roughly 90% of the stolen $3.5 million had been recovered or frozen, leaving a net loss of approximately $200,000.”
reviewerNet loss approximately $200,000 after ~90% recoveryMatches the April 27 report but later recovery updates put the net loss near $60K. The page is stale on this figure and should say the later figure.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“In April 2026, three of its vaults were exploited via a compromised admin private key, resulting in approximately $3.5 million in losses across WBTC, XAUm, and USDC holdings.”
reviewerApproximately $3.5M drained from three vaults (WBTC, XAUm, USDC) via compromised admin keyConsistent across sources. - #2[confirmed][no action needed]in section: Security Exploit — April 2026
“The attacker address identified on-chain was 0xe76970bbf9b038974f6086009799772db5190f249ce7d065a581b1ac0adaef75.”
reviewerFunction name and attacker addressMatches the cited article. - #5[confirmed][no action needed]in the timeline
“Volo reports approximately 90% of stolen funds recovered or frozen; net loss estimated at approximately $200,000. Full user compensation pledged from Treasury.”
reviewerNet loss in timelineAccurate for April 27; the later update belongs in a new timeline entry. - #8[confirmed][no action needed]in section: Audit History
“Prior to the April 2026 exploit, Volo Protocol's smart contracts were audited by Ottersec, Movebit, and Hacken.”
reviewerPrior audits by Ottersec, Movebit, and HackenMatches the cited article.