← Purrlendreviewed 2026-11-02 · 12 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Purrlend 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
5 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #3[unverifiable][awaiting moderator]in section: April 2026 Exploit: Multisig Permission Breach
“The attack originated from a suspicious admin multisig transaction executed at approximately 1:20 a.m. UTC”
reviewerMultisig transaction occurred at approximately 1:20 a.m. UTCExact 1:20 a.m. UTC not found in fetched sources (mexc/livebitcoinnews not read). Also internally odd: 1:20 plus ~8h is ~9:20, near the 9:10 pause time. - #5[unverifiable][awaiting moderator]in section: Insider Allegations and Unknown Attacker Identity
“Following the exploit, community members alleged the incident may have been an inside job”
reviewerCommunity members alleged an inside jobNo fetched source documents community inside-job allegations. The page does hedge that none is confirmed. - #6[unverifiable][awaiting moderator]in section: Insider Allegations and Unknown Attacker Identity
“No law enforcement referral or on-chain asset freeze has been reported.”
reviewerNo law enforcement referral has been reportedOne search summary claimed Purrlend said it was working with law enforcement, but I could not confirm that in a fetched source. Negative claim is unconfirmed either way. - #11[unverifiable][awaiting moderator]in the summary
“As of late May 2026, the protocol remains paused with no published post-mortem, recovery plan, or user compensation details.”
reviewerAs of late May 2026 the protocol remains paused with no post-mortemNo later reporting found either way; the page is now about five months old (today 2026-11-02), so this status is dated. - #12[unverifiable][awaiting moderator]in the timeline
“HyperEVM mainnet launches, enabling new DeFi deployments on Hyperliquid's EVM layer.”
reviewerHyperEVM mainnet launched February 2025No source cited and I did not verify it; the timeline entry has an empty source.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: April 2026 Exploit: Multisig Permission Breach
“On MegaETH, approximately $324,549 was drained in USDT0, WETH, and USDm.”
reviewerMegaETH loss was about $324,549$324,549 matches the total minus HyperEVM, but sources show an unreconciled ~$163K MegaETH figure (163,169 USDT0). Per-token breakdown not reconciled. - #4[partially supported][awaiting moderator]in section: April 2026 Exploit: Multisig Permission Breach
“At approximately 9:10 a.m. UTC on April 25, Purrlend paused all protocol operations”
reviewerPurrlend paused around 9:10 a.m. UTC and posted a statementPause and quote confirmed; ourcryptotalk gives about 9:10 UTC, but 09:10 also appears as a publication timestamp in another outlet, so the time may be a conflation. - #8[partially supported][awaiting moderator]in section: Governance and Security Design Failures
“The absence of timelock protections on privileged multisig operations represents a significant governance failure that the community has highlighted as the primary enabling condition for the exploit.”
reviewerCommunity highlighted the missing timelock as the primary enabling condition; characterized as a significant governance failureSource notes the lack of a timelock but not a community consensus on it being the primary cause; the page also says the root cause (key compromise vs insider) is unknown. Editorial overstatement. - #9[partially supported][awaiting moderator]in section: April 2026 Exploit: Multisig Permission Breach
“The protocol's total value locked collapsed from roughly $1.5 million to approximately $444,000 following depositor flight.”
reviewerTVL fell from about $1.5M to about $444,000Figures match, but the fall coincides with a $1.5M theft, so 'depositor flight' as the cause is an unsupported attribution. The summary's '70%' is roughly consistent (about 70%).
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: April 2026 Exploit: Multisig Permission Breach
“On April 25, 2026, Purrlend lost approximately $1,522,038 across its HyperEVM and MegaETH deployments”
reviewerPurrlend lost approximately $1,522,038 across HyperEVM and MegaETH on April 25, 2026Total and HyperEVM figures are consistent across sources. - #7[confirmed][no action needed]in section: Governance and Security Design Failures
“Purrlend operated a 2-of-3 admin multisig without any timelock mechanism.”
reviewerMultisig was 2-of-3 with no timelock; bridge role inherited elevated permissionsSingle outlet, but matches the page. - #10[confirmed][no action needed]in section: April 2026 Exploit: Multisig Permission Breach
“The exploit was first publicly flagged by on-chain investigator Kirby Ong, founder of HypurrCollective.”
reviewerKirby Ong, founder of HypurrCollective, first flagged the exploitConfirmed.
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.