Fact-check findings
What an automated fact-checker found when it re-read Typus Perp 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
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Team Response and Recovery Status
“The protocol's TVL as of May 2026 stands at approximately $126,420 on DeFiLlama, a dramatic reduction from the pre-exploit level of over $3.67 million.”
reviewerProtocol TVL as of May 2026 is about $126,420 on DeFiLlama.Historical May 2026 value could not be read. The figure is dated and the current TVL appears far lower. - #5[unverifiable][awaiting moderator]in section: Team Response and Recovery Status
“The Typus team was alerted to the attack at 13:24 UTC and paused all smart contracts at 13:39 UTC, approximately 15 minutes after notification and 34 minutes after the first malicious transaction.”
reviewerTimeline of response (alert 13:24, pause 13:39, Sui Foundation 13:48, law enforcement 14:54 UTC) and 15% bounty offer.Primary post-mortem was blocked. The 34 minutes figure is consistent with a 13:05 start (13:39 minus 13:05).
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Unaudited Contract — Critical Governance Failure
“The vulnerable oracle contract package was deployed on November 13, 2024, but was explicitly excluded from the scope of Typus Finance's May 2025 security audit conducted by MoveBit.”
reviewerThe vulnerable oracle module was excluded from the May 2025 MoveBit audit and was deployed November 13, 2024.Both the deploy date and the audit exclusion are stated in the fetched article. - #2[confirmed][no action needed]in section: Broader Sui Ecosystem Context
“The first was the Cetus Protocol hack in May 2025, in which the primary Sui DEX lost over $220 million.”
reviewerCetus lost over $220 million in May 2025 and total Sui losses in 2025 exceeded $225 million.Supported. - #3[confirmed][no action needed]in section: Broader Sui Ecosystem Context
“resulting in a $2.6 million loss”
reviewerNemo Protocol exploit caused a $2.6 million loss.Figure varies between $2.4M (early) and $2.6M (Nemo report); the page's figure is supportable. - #6[confirmed][no action needed]in section: Oracle Manipulation Exploit — October 2025
“On October 15, 2025, Typus Perp's TLP (Typus Liquidity Pool) contract was drained of approximately $3.44 million USD in a targeted oracle manipulation attack.”
reviewerThe 2025-10-15 oracle exploit drained about $3.44 million.The amount matches. The technical details (update_v2, asset amounts) were not independently re-read.