Summer Finance Pauses Vaults After $65.4M Flash Loan Attack Triggers $6M Loss

Security Firms Flag Breach

Blockchain security firms reported Monday, July 6, a major security breach targeting Summer Finance, a decentralized finance ( DeFi) yield optimization protocol. According to real-time onchain analytics flagged by security monitors, the protocol suffered an estimated loss of $6 million from a sophisticated flash loan and price manipulation attack.

Following the alerts, the Summer Finance team confirmed the breach, stating:

“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. We will provide more updates as we have them.”

The exploit involved a multi-step manipulation of the protocol’s accounting logic. An analysis by blockchain security firm Certik revealed that the attacker initiated a $65.4 million flash loan to distort the asset valuation framework of the Lazy Summer Protocol vault, which is managed under Summer.fi.

By exploiting a vulnerability in the Fleet Commander contract’s asset accounting logic, the attacker artificially skewed how the system calculated token value. After depositing roughly $64.8 million into the manipulated ecosystem, the actor executed an arbitrage maneuver to redeem $70.9 million in assets.

According to Cyvers, the exploiter rapidly swapped the resulting $6 million profit into DAI stablecoins before funneling the stolen funds into an attacker-controlled wallet to break the paper trail.

While Summer Finance developers investigate the underlying vulnerabilities to release a comprehensive post-mortem report, the incident highlights a rising trend of complex, infrastructure-level arbitrage manipulation. Meanwhile, security experts urged participants to take immediate defensive precautions, including revoking permissions or canceling any active smart contract approvals tied to the affected Lazy Summer Protocol vaults.

Experts also advised participants to verify all communications exclusively through official project channels to avoid phishing attacks, and to consider moving digital assets out of online “hot” wallets into offline cold storage until the core development teams patch the underlying protocols.