← zkLendreviewed 2026-11-01 · 9 claims checked
Fact-check findings
What an automated fact-checker found when it re-read zkLend 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
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #9[unverifiable][awaiting moderator]in section: Protocol Overview
“zkLend was founded in February 2022 by Brian Fu, who brought over 15 years of traditional finance experience from Bloomberg and Standard Chartered Bank, and Jane Ma, who previously worked in Sales and Trading at Credit Suisse and as Chief of Staff at Deliveroo Hong Kong.”
reviewerFounders and background claims (Brian Fu, Jane Ma; prior employers; founded Feb 2022; mainnet launch Oct 19, 2023).Biographical details were not verified within the sources I fetched; the cited press-release pages were not fetched in this pass.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: Protocol Response, Bounty and Compensation Plan
“A $500,000 bounty for information leading to the attacker's capture was reportedly maintained.”
reviewerA $500,000 bounty for information leading to the attacker's capture was maintained.Search snippets from secondary outlets mention a $500,000 bounty, but neither cited shutdown source I fetched states it. The hedge 'reportedly' is appropriate. - #5[partially supported][awaiting moderator]in section: February 2025 Exploit
“Reports differ on the timing: the zklend page, citing zkLend's post-mortem, BlockSec, Halborn, Rekt News, CoinTelegraph and CryptoSlate, places the exploit on February 11–12, 2025, while the zklend-starknet page, citing BlockSec, Halborn and Rekt News, gives February 12, 2025.”
reviewerPage contains unresolved cross-page editorial text about discrepancies between 'the zklend page' and 'the zklend-starknet page'.The underlying date range is fair (Feb 12 is the most widely reported exploit date, disclosure Feb 11), but the prose refers to internal page names, which are not sources; the page should state the date directly. - #7[partially supported][awaiting moderator]in the cited sources
“https://web.archive.org/web/20261028164604/https://u.today/ripple-president-explains-why-robinhood-chose-rlusd-stablecoin”
reviewerU.Today source URL supports Railgun / Vitalik discussion.Live source is fine, but the stored archive_url points to an unrelated Ripple/Robinhood article (archived redirect junk). Archive snapshot should be replaced; not edited here because no verified replacement was fetched. - #8[partially supported][awaiting moderator]in section: Alleged Link to the EraLend Exploit
“The alleged link points to a repeat threat actor, but it rests on on-chain forensics; the attacker has not been publicly identified and no law-enforcement confirmation has been reported.”
reviewerSlowMist alleges link to EraLend; attacker not identified and no law-enforcement confirmation reported.No arrest or attribution confirmed; but zkLend stated it was cooperating with law enforcement, which the page does not mention. SlowMist article itself not fetched in this review.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Protocol Response, Bounty and Compensation Plan
“On June 25, 2025, about four months after the exploit, zkLend announced it was permanently winding down operations.”
reviewerzkLend announced a permanent wind-down on June 25, 2025 and allocated remaining ~$200,000 treasury to a user recovery fund.Date, wind-down, delisting reason and $200K treasury are supported by multiple reachable outlets. - #3[confirmed][no action needed]in section: Attacker Fund Movements and Laundering Attempts
“The attacker attempted to launder 706.4 WETH through Railgun, an Ethereum privacy protocol, but Railgun's compliance and exclusion policies returned the funds to the originating address.”
reviewerAttacker deposited 706.4 WETH into Railgun, which returned funds to the originating address.Supported by Rekt and U.Today. - #4[confirmed][no action needed]in section: February 2025 Exploit
“In February 2025 an attacker drained approximately $9.57 million from zkLend through the protocol's wstETH market.”
reviewerApproximately $9.57 million drained; Rekt reports $9.57M.Figure matches Rekt; other outlets say about $9.5M, consistent. - #6[confirmed][no action needed]in section: Attacker Fund Movements and Laundering Attempts
“The attacker then tried to use Tornado Cash and deposited 2,930 ETH (roughly $5.4 million at the time) into a phishing site impersonating the Tornado Cash frontend (tornadoeth.cash), losing those funds to the site's operators.”
reviewerAttacker's stolen ETH was lost to a Tornado Cash phishing site, 2,930 ETH.Corroborated across search results; the attacker's own claim, which the page attributes appropriately. The Rekt article does not cover this event.
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.