← Curioreviewed 2026-11-02 · 10 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Curio 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
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: Recovery Efforts
“An airdrop equal to 10% of the CurioDAO Treasury was promised as a bonus to all customers.”
reviewerTreasury airdrop of 10% and per-network direct losses of about $180k ($113k Ethereum, $38k BSC, $28k SKALE, $1k Boba)The primary Medium post is blocked. A secondary search found nothing on the airdrop or the $113k and $180k figures. Not scored. - #8[unverifiable][awaiting moderator]in section: Background
“Verboonen is a member of the Forbes Technology Council.”
reviewerFounder Verboonen biographical details (ETH Zurich, Forbes Technology Council, Qualcomm-acquired startup)I did not fetch the Venturelab or Crunchbase pages in this review, and the page marks them unarchivable. The biography is neither confirmed nor refuted. It is based on self-reported sources.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: The Exploit
“Using an attack contract, the attacker invoked the `cook` function, which leveraged the `IDSChief` and `IDSPause` contracts”
reviewerAttack used cook, IDSChief/IDSPause, plot, and delegatecall to an exec libraryThe plot/delegatecall mechanics are confirmed. The cook/IDSChief detail is not on the cited Halborn page. I did not check it against the Hacken or Neptune Mutual writeups. - #5[partially supported][awaiting moderator]in section: Recovery Efforts
“Curio offered 10% of any recovered funds to white hat hackers who assisted in fund recovery.”
reviewerRecovery plan includes a white hat bounty of 10% of any recovered fundsSecondary reports describe a tiered bounty (10% in week one, 5% after). The page gives a flat 10%. The primary source could not be read, so the correction rests on REKT and a search summary. - #7[partially supported][awaiting moderator]in section: Recovery Efforts
“Each stage would deliver 25% of documented losses, with full compensation projected within one year of the exploit.”
reviewerLP compensation in four 90-day stages of 25% each, paid in USDC/USDTThe 25% per 90 days structure appears in a secondary report. Sources differ on the number of stages. The full fetch was not done. - #10[partially supported][awaiting moderator]in the timeline
“Curio announces CGT 2.0 token publicly, pledging 100% restoration for pre-exploit CGT holders across all affected networks.”
reviewerCGT 2.0 announced March 26, 2024 pledging 100% restorationThe March 26 date is the date of the press coverage. The plan itself was announced March 25, as the page's own timeline shows.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“Curio (CurioDAO) is a multi-chain real-world asset (RWA) DeFi protocol that suffered a critical smart contract exploit on March 23, 2024, resulting in approximately $16 million in losses”
reviewerExploit on March 23, 2024 caused about $16 million in losses via voting-power privilege escalation minting about 1 billion CGTDate, loss figure and mint size are supported by REKT and Halborn. - #2[confirmed][no action needed]in section: On-Chain Evidence
“**Attacker Address:** `0xdaAa6294C47b5743BDafe0613d1926eE27ae8cf5`”
reviewerAttacker address and attack transaction hashAddress, tx hash and the 996 billion retained figure match REKT. Halborn does not list them, so the section's attribution to Hacken is not checked.citedrekt.news/curio-rekt - #4[confirmed][no action needed]in section: The Exploit
“Halborn noted that the project relied on internal security reviews rather than external audits.”
reviewerHalborn noted the project relied on internal security reviews; REKT said no known audits could be foundBoth quotes are supported in substance. - #9[confirmed][no action needed]in section: On-Chain Evidence
“No independent law enforcement seizure or on-chain recovery of funds has been publicly confirmed as of the time of this report.”
reviewerNo law enforcement action or fund recovery has been publicly confirmedConsistent with available reporting. This is an absence claim.citedrekt.news/curio-rekt
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.