EraLend Hack

TOTAL LOST $3.4M
Medium Reentrancy zksync era

Summarize with AI

Affected Chain zksync era Incident surface
Recovered - No recovery reported
All-Time Rank #516 By amount stolen
Auditors 1 Prior security audit

Incident Overview

EraLend, a zkSync Era lending protocol, was exploited via a read-only reentrancy attack, leading to a loss of approximately 3,400,000 $USD.

EraLend, a lending protocol on zkSync Era, fell victim to an exploit. The root cause has been identified as a read-only reentrancy attack, which resulted in a substantial loss of around 3,400,000 $USD.

Attacker Address: https://explorer.zksync.io/accounts/0xf1D076c9…5ECE7a

Malicious Transactions:

https://explorer.zksync.io/transactions/0x99efebac…4ab0ef

https://explorer.zksync.io/transactions/0x7ac4da1e…8bfe98

Malicious Contracts:

https://explorer.zksync.io/address/0x7d8772DC…F335F0

https://explorer.zksync.io/address/0xC5c668Dc…338035

Incident Report

Protocol / Project EraLend
Date of Incident
Affected Chain(s) zksync era
Attack Technique Reentrancy
Classification Protocol Logic / Borrowing and Lending
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Smart Contract Language Solidity
Official Website www.eralend.com/
Protocol Twitter/X @Era_Lend
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
DeFi Lending & Borrowing Linea Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of reentrancy and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with zksync era smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in EraLend's contract logic - root cause: protocol logic / borrowing and lending
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review
Audited by Audit Report 1 — still lost $3.4M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to EraLend, these are the critical security checks that could have prevented this incident (July 2023).

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Reentrancy examples →

Sources & References

Learn to Prevent the Next EraLend

The EraLend hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial