Fact-check findings
What an automated fact-checker found when it re-read Summer.fi Lazy Summer Exploit (July 2026) 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.
disputed
5 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #4[disputed][awaiting moderator]in section: Background: Summer.fi and Lazy Summer Protocol
“In August 2023, the company closed a $6 million Series A funding round led by Libertus Capital.”
reviewerIn August 2023, Summer.fi closed a $6 million Series A funding round led by Libertus Capital.Three independent sources (original 2022 press release, CryptoSlate syndication, and CoinCarp's fundraising database) agree the identical $6M/Libertus Capital round closed in April 2022, not August 2023. The cited CoinCodex interview is also now dead (see link-rot finding), so there is no live source to recheck its original framing; this appears to be a date error of about 13 months.Proposed correction (not yet applied)In April 2022, the company closed a $6 million Series A funding round led by Libertus Capital. - #5[disputed][awaiting moderator]in the timeline
“2023-08”
reviewerSummer.fi closed a $6 million Series A funding round led by Libertus Capital (timeline entry dated 2023-08).Same underlying error as the section-1 prose: the Series A actually closed in April 2022 (while the company was still named Oasis.app, pre-rebrand), not August 2023.Proposed correction (not yet applied)2022-04 - #13[disputed][awaiting moderator]in the timeline
“2025-11-07”
reviewerStream Finance's collapse that triggered this chain of events occurred on November 7, 2025.Multiple independent reports place the loss disclosure and xUSD depeg on November 3-4, 2025, not November 7. The page's own cited CryptoTimes piece links to a source dated November 4, 2025. Proposed correction uses November 4 as the best-supported date, acknowledging some sources favor November 3.Proposed correction (not yet applied)2025-11-04 - #24[disputed][awaiting moderator]in section: Market Impact: SUMR Token
“The SUMR governance token, which had begun trading on January 21, 2026, declined by more than 18% immediately following public disclosure of the exploit on July 6, 2026. Trading data noted the token near $0.00193 in the 24-hour period following the incident.”
reviewerThe SUMR governance token declined by more than 18% immediately following public disclosure of the exploit, with trading data showing the token near $0.00193 in the 24-hour period following the incident.The page splices two different reported data points that do not belong together: an 18% decline figure (associated elsewhere with a ~$0.0016 price) and a $0.00193 price point that two independent sources (including the page's own cited BeInCrypto article) tie to only a ~5% decline. As written, the sentence pair is internally inconsistent with its own cited source.Proposed correction (not yet applied)The SUMR governance token, which had begun trading on January 21, 2026, declined by more than 5% immediately following public disclosure of the exploit on July 6, 2026. Trading data noted the token near $0.00193 in the 24-hour period following the incident. - #25[disputed][awaiting moderator]in the timeline
“SUMR token declines by more than 18% following public disclosure of the exploit.”
reviewerSUMR token declines by more than 18% following public disclosure of the exploit (timeline entry).Same underlying figure-mismatch as the Market Impact section; the cited BeInCrypto source reports roughly 5% not 18%.Proposed correction (not yet applied)SUMR token declines by more than 5% following public disclosure of the exploit.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #18[unverifiable][awaiting moderator]in section: Attack Mechanism and Execution
“Stolen USDC was subsequently swapped to DAI via Curve and transferred to the attacker's beneficiary address at 0x7BF716167B48CF527725722C6d79494b45B3BDCa, executed through a contract at 0x0514F827C129C16418a0933E03C99A6AF982FC61.”
reviewerStolen USDC was swapped to DAI via Curve and transferred to attacker address 0x7BF716167B48CF527725722C6d79494b45B3BDCa, executed through contract 0x0514F827C129C16418a0933E03C99A6AF982FC61.The general laundering mechanism (swap to DAI via Curve) is independently confirmed, but I could not independently verify the two specific on-chain addresses against a block explorer; no secondary source I found repeats both exact strings. - #19[unverifiable][awaiting moderator]in section: Detection and Incident Response
“Blockaid issued the first public alert at approximately 05:36 AM UTC on July 6, 2026, roughly 19 minutes after the exploit executed.”
reviewerBlockaid issued the first public alert at approximately 05:36 AM UTC on July 6, 2026, roughly 19 minutes after the exploit executed, and Block Analitica froze deposit caps at 06:42 AM UTC while the Guardian multisig completed a full pause at 10:25 AM UTC and the Foundation swept donated stale tokens at 16:39 PM UTC.The broad sequence (Blockaid first, then PeckShield/CertiK, then a full pause) is corroborated elsewhere, but the precise minute-level timestamps in this and related sentences could not be independently checked because the cited official post-mortem was unreachable (503) throughout this review. - #20[unverifiable][awaiting moderator]in section: Detection and Incident Response
“Block Analitica, the vault manager, froze deposit caps at 06:42 AM UTC.”
reviewerBlock Analitica froze deposit caps at 06:42 AM UTC; PeckShield and CertiK confirmed the attack.Block Analitica's role is confirmed; the exact timestamp is not independently checkable because the primary post-mortem was unreachable (503). - #26[unverifiable][awaiting moderator]in section: Detection and Incident Response
“Summer.fi acknowledged the incident publicly, stating on X: 'We are aware of the reported exploit a little earlier today and are investigating the root cause. The protocol guardians are currently pausing all Vaults across the Lazy Summer Protocol.'”
reviewerSummer.fi stated on X that it was aware of the exploit, was investigating, and that protocol guardians were pausing all Vaults across the Lazy Summer Protocol.The substance (acknowledgment + pause) is corroborated; I could not independently verify this is a verbatim quote, since no source URL for the X post itself is given and I did not have access to X/Twitter.
link rot
5 claimsA cited source no longer resolves or no longer says what the page attributes to it.
- #6[link rot][awaiting moderator]in section: Background: Summer.fi and Lazy Summer Protocol
“https://coincodex.com/article/31177/shaping-defis-horizon-a-conversation-with-chris-bradbury-ceo-of-summerfi”
reviewerCoinCodex interview with CEO Chris Bradbury is a live, checkable source for the spinout and Series A claims.Dead link, no archive_url recorded for it in sources_used. Underlying facts were independently re-verified via other sources (see related findings). - #7[link rot][awaiting moderator]in the timeline
“https://coincodex.com/article/31177/shaping-defis-horizon-a-conversation-with-chris-bradbury-ceo-of-summerfi”
reviewerTimeline source for the 2021-06 spinout (CoinCodex) is live.Same dead URL reused as the timeline source for the spinout event. - #8[link rot][awaiting moderator]in the timeline
“https://coincodex.com/article/31177/shaping-defis-horizon-a-conversation-with-chris-bradbury-ceo-of-summerfi”
reviewerTimeline source for the 2023-08 Series A entry (CoinCodex) is live.Same dead URL reused as the timeline source for the (also disputed) Series A date. - #28[link rot][awaiting moderator]in section: Fund Movement and Laundering
“https://bitcoinworld.co.in/summer-fi-hacker-laundering-dai-tornado-cash/”
reviewerFund-movement source: bitcoinworld.co.in article on the hacker laundering DAI through Tornado Cash is a live, checkable source.Dead link; this URL is also absent from the page's own sources_used archive list, so no archived snapshot exists to fall back on. The underlying facts are otherwise covered by the still-live Defiant and Crypto Briefing citations in the same section. - #29[link rot][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260730080212/https://moneycheck.com/cardano-ada-rallies-31-from-multi-year-lows-is-more-upside-ahead/”
reviewerThe archived snapshot recorded for the MoneyCheck source (sources_used) corresponds to the cited Summer.fi exploit article.The archive_url stored for this source captured the wrong page entirely, apparently an archiving/snapshot error. The live URL itself is fine (confirmed working), so the citation is not broken in practice, but the stored archive record for it is wrong and should not be relied on for tamper-evidence purposes. I attempted to query the Wayback Machine's availability API for a correct snapshot but was rate-limited (HTTP 429) and could not obtain a verified replacement archive URL; recommend regenerating the archive_url for the correct page rather than leaving the mismatched one in place.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #10[partially supported][awaiting moderator]in section: Background: Summer.fi and Lazy Summer Protocol
“In January 2026, the SUMR governance token was introduced and began trading on January 21, 2026, tied to protocol revenue and on-chain governance rights.”
reviewerThe SUMR governance token was introduced in January 2026 and began trading on January 21, 2026.The page's January 21, 2026 date matches the TGE, but Summer.fi's own announcement says open trading started the next day, January 22. A minor, low-stakes discrepancy; not corrected given the ambiguity in primary-source framing. - #23[partially supported][awaiting moderator]in section: Fund Movement and Laundering
“According to reporting by The Defiant and confirmed in Summer.fi's post-mortem, the attacker moved approximately $1.35 million in DAI by swapping it for ETH on Uniswap and routing it through an intermediary wallet into Tornado Cash. As of reporting, approximately $4.67 million in DAI remained in the original attacker wallet.”
reviewerThe attacker moved approximately $1.35 million in DAI by swapping it for ETH on Uniswap and routing it through an intermediary wallet into Tornado Cash, leaving approximately $4.67 million in DAI in the original wallet.The $1.35M headline figure is well-supported; the more granular mechanism (Uniswap, single intermediary wallet) and the precise $4.67M remaining balance are arithmetically consistent (6.017M - 1.35M = 4.667M) but I could not independently confirm these specifics beyond the cited source, whose full text did not load.
confirmed
14 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Background: Summer.fi and Lazy Summer Protocol
“Summer.fi originated as Oasis.app, built within the Maker Foundation as the original front-end for the Maker Protocol starting in 2016.”
reviewerOasis.app was built within the Maker Foundation as the original front-end for the Maker Protocol starting in 2016.2016 origin as the Maker-affiliated Oasis front-end is corroborated by an independent aggregator profile, consistent with the official rebrand blog. - #2[confirmed][no action needed]in section: Background: Summer.fi and Lazy Summer Protocol
“Following the Maker Foundation's decentralization in 2021, Oasis.app was spun out as an independent company.”
reviewerOasis.app was spun out as an independent company in June 2021 following the Maker Foundation's decentralization.Independently corroborated outside the (now-dead) CoinCodex source. - #3[confirmed][no action needed]in section: Background: Summer.fi and Lazy Summer Protocol
“In June 2023, it rebranded to Summer.fi, expanding from a MakerDAO-centric product to a multi-protocol DeFi interface supporting Aave, Morpho, Compound, and others.”
reviewerOasis.app rebranded to Summer.fi in June 2023.Confirmed by an independent aggregator in addition to the official blog. - #9[confirmed][no action needed]in section: Background: Summer.fi and Lazy Summer Protocol
“The Lazy Summer Protocol — an automated yield vault system — was launched in early 2025.”
reviewerThe Lazy Summer Protocol, an automated yield vault system, was launched in early 2025.Confirmed via an independent February 2025 press release. - #11[confirmed][no action needed]in section: Background: Summer.fi and Lazy Summer Protocol
“Prior to the July 2026 exploit, Summer.fi had no publicly documented major security incidents since its 2023 rebrand.”
reviewerPrior to the July 2026 exploit, Summer.fi had no publicly documented major security incidents since its 2023 rebrand.Corroborated by independent reporting. - #12[confirmed][no action needed]in section: Root Cause: Stale Valuation Inherited from the Stream Finance Collapse
“The exploit's underlying precondition traces to the November 2025 collapse of Stream Finance, in which an external fund manager disclosed a $93 million loss, causing Stream's stablecoin xUSD to lose approximately 77% of its value and triggering an estimated $285 million in contagion across DeFi lending platforms including Euler, Silo, and Morpho.”
reviewerStream Finance's November 2025 collapse involved a $93 million loss disclosure, xUSD losing approximately 77% of its value, and an estimated $285 million in contagion across Euler, Silo, and Morpho.Well-corroborated by independent reporting outside the cited sources. - #14[confirmed][no action needed]in section: Root Cause: Stale Valuation Inherited from the Stream Finance Collapse
“The Lazy Summer Protocol had begun the process of decommissioning this Ark (strategy adapter) by setting its deposit cap to zero, but the Ark remained counted in the Fleet Commander contract's totalAssets() calculation, meaning its stale, inflated valuation continued to be incorporated into vault share pricing.”
reviewerSilo 'Varlamore USDC Growth' vault tokens were never marked down on-chain after the Stream Finance collapse, and the Ark remained counted in totalAssets() despite its deposit cap being set to zero, leaving a dormant mispricing vulnerability for roughly eight months.Root-cause mechanism is independently corroborated by multiple security researchers beyond the cited sources. - #15[confirmed][no action needed]in section: Attack Mechanism and Execution
“According to Summer.fi's official post-mortem and independent security analysis, the attacker began positioning for the exploit at least three months in advance, with wallets funded through a common path in early April 2026, systematically accumulating the stale-valued Silo Varlamore USDC Growth tokens.”
reviewerThe attacker began positioning at least three months in advance, with wallets funded through a common path in early April 2026.Corroborated by independent reporting on the same post-mortem. - #16[confirmed][no action needed]in section: Attack Mechanism and Execution
“The primary affected vault was LazyVault_LowerRisk_USDC (managed by Block Analitica), from which approximately $5.64 million was extracted, with an additional approximately $0.40 million drained from the LazyVault_HigherRisk vault. Total extracted funds amounted to approximately $6.04 million in USDC.”
reviewerThe attacker used a $65.4 million flash loan sourced from Morpho to redeem shares at an inflated price, extracting a total of approximately $6.04 million (about $5.64M from LazyVault_LowerRisk_USDC and $0.40M from LazyVault_HigherRisk).Figures are consistent across independent outlets; minor variance in the flash-loan-vs-deposit figure ($65.4M vs $64.8M) across sources is normal day-one reporting noise and does not contradict the page. - #17[confirmed][no action needed]in section: Attack Mechanism and Execution
“During the exploit, the vault's displayed APY briefly surged to approximately 2.08 million percent, an anomaly flagged by on-chain monitoring.”
reviewerDuring the exploit, the vault's displayed APY briefly surged to approximately 2.08 million percent.Confirmed by an independent outlet. - #21[confirmed][no action needed]in section: Detection and Incident Response
“The protocol had a reported total value locked of approximately $22 million at the time of the incident.”
reviewerThe protocol had a reported total value locked of approximately $22 million at the time of the incident.Confirmed. - #22[confirmed][no action needed]in section: Fund Movement and Laundering
“Following the exploit, the attacker's beneficiary wallet (0x7BF716167B48CF527725722C6d79494b45B3BDCa) received approximately 6.017 million DAI.”
reviewerThe attacker's beneficiary wallet received approximately 6.017 million DAI, of which approximately $1.35 million was moved into Tornado Cash via Uniswap and an intermediary wallet, leaving approximately $4.67 million in the original wallet.The 6.017M DAI figure is corroborated by two independent outlets beyond the cited Defiant piece. - #27[confirmed][no action needed]in section: Protocol Remediation and Governance Transition
“Approximately $4 million in user assets remained outstanding and temporarily illiquid. Summer.fi also announced that its application would remain operational through August 31, 2026, with customer support via email and Discord through that date. After August 2026, responsibility for the Lazy Summer Protocol infrastructure was stated to shift entirely to the Lazy Summer DAO.”
reviewerFollowing the incident, all Lazy Summer Protocol vaults remained paused; the root cause was incomplete Ark decommissioning; approximately $4 million in user assets remained outstanding and temporarily illiquid; the app would remain operational through August 31, 2026 with support via email and Discord, after which responsibility shifts to the Lazy Summer DAO.Strongly corroborated, including near-exact figures, by two independent outlets. Minor naming variance noted: one source calls it the 'Lazy Protocol DAO' rather than 'Lazy Summer DAO,' which is not treated as a material dispute. - #30[confirmed][no action needed]in section: Systemic Risk: DeFi Composability and Stale Oracle Contagion
“The Crypto Times described the dynamic as follows: 'in composable DeFi, a collapse is never fully over: the mispriced debris it leaves behind can sit dormant on-chain for months, waiting for someone patient enough to turn it into a weapon.'”
reviewerSecurity researchers described the exploit as illustrating DeFi composability risk, quoting CryptoTimes: 'in composable DeFi, a collapse is never fully over: the mispriced debris it leaves behind can sit dormant on-chain for months, waiting for someone patient enough to turn it into a weapon.'Quote verified against the cited source.