The decentralized finance protocol dForce suffered a significant security breach on February 10, 2023, losing approximately $3.6 million in a sophisticated reentrancy attack targeting its wstETH/ETH Curve vaults on both Arbitrum and Optimism. The exploit marks yet another reminder that DeFi remains a prime target for malicious actors, even as the broader crypto market trades at Bitcoin around $21,651 and Ethereum near $1,514.
The Exploit Mechanics
The attacker exploited a read-only reentrancy vulnerability embedded in the Curve pool integration used by dForce. In a read-only reentrancy scenario, the attacker manipulates the internal state of a smart contract during an ongoing external call, effectively tricking the protocol into reading stale or corrupted price data. Unlike standard reentrancy attacks that directly drain funds, this variant manipulates price oracles to create favorable liquidation conditions.
Specifically, the attacker leveraged the vulnerability to manipulate the wstETH/ETH price within dForce vaults. This price distortion triggered the liquidation of 1,031.42 ETH on Arbitrum and approximately 30.31 ETH equivalent of wstETH/ETH Curve LP tokens on Optimism. Additionally, the attack generated roughly $2.3 million in protocol debt, compounding the financial damage.
Blockchain security firm PeckShield was among the first to flag the incident publicly, identifying the attack vector within hours of its execution. The read-only reentrancy approach is particularly insidious because it does not trigger traditional reentrancy guards, making it harder to detect during routine audits.
Affected Systems
The exploit was confined to dForce wstETH/ETH Curve vaults operating on both Arbitrum and Optimism layer-2 networks. dForce confirmed that the vulnerability was specific to these vaults and that user funds deposited into dForce Lending and other vault types remained unaffected. The protocol team immediately paused all vaults upon detecting the exploit, a swift response that likely prevented further losses.
This is not the first time dForce has been targeted. In 2021, the protocol suffered a $25 million exploit, though the attacker subsequently returned approximately $24 million of the stolen funds. The recurrence underscores the persistent security challenges facing DeFi platforms that integrate with multiple external protocols and price oracles.
The Mitigation Strategy
In response to the attack, dForce took several immediate steps. First, the team paused all vault contracts to halt any ongoing or follow-on exploitation. Second, the vulnerability was identified and isolated to the wstETH/ETH Curve pool integration. Third, the protocol communicated transparently with its user base via social media, providing real-time updates on the scope of the damage and the status of remediation efforts.
For the broader DeFi ecosystem, the dForce exploit reinforces the critical importance of comprehensive reentrancy protection, including read-only reentrancy guards that go beyond standard checks. Protocols that integrate with external price feeds, particularly those from Curve pools, should implement multi-layered validation to ensure price data integrity even during ongoing contract calls.
Lessons Learned
The dForce incident is part of a troubling trend. According to data from TRM Labs, approximately $3.7 billion was stolen across crypto hacks in 2022, with DeFi protocols accounting for roughly 80% of all losses. The read-only reentrancy vector has emerged as a particularly dangerous attack surface because it bypasses conventional security measures.
Key lessons from this exploit include the necessity of third-party smart contract audits with specific focus on oracle manipulation and reentrancy patterns, the importance of rapid incident response protocols, and the value of maintaining isolated vault architectures that limit blast radius when an exploit occurs.
User Action Required
Users who had funds deposited in dForce wstETH/ETH Curve vaults on Arbitrum or Optimism should monitor official dForce communications for updates on fund recovery and compensation plans. All DeFi users, regardless of platform, should consider diversifying across multiple protocols, avoiding excessive concentration in any single vault or pool, and staying informed about the security posture of platforms they use. The crypto market, with Bitcoin trading near $21,651 and total market capitalization under pressure, rewards vigilance in an environment where exploits remain a persistent threat.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Always conduct your own research before engaging with any DeFi protocol.
read only reentrancy on a Curve integration in 2023. Curve explicitly warned about this pattern in their docs. dForce either didnt read or didnt care
read-only reentrancy is the scariest class of bug. contract passes every audit because the vulnerability lives in the external call assumption not the code itself
read_only_rekt_ exactly. auditors flag reentrancy guards on internal functions but external Curve calls during a withdrawal are considered safe by convention. that convention cost 3.6M
read-only reentrancy is the scariest exploit class because the contract looks totally fine on static analysis
read_only_wtf you nailed it. the contract passes every slither check because external calls are read-only by definition. the exploit is in the state change between the view call and the internal update
exactly this. static analysis catches maybe 60% of reentrancy variants. the read-only kind is basically invisible to most auditing tools
60% is generous. most static analyzers dont even model cross-contract state changes. read-only reentrancy lives in the gap between what tools check and what actually executes
segfault exactly. read-only reentrancy is invisible to most static analyzers. that’s what makes it so dangerous
read_only_wtf you nailed it. the contract passes all slither checks because external calls are read-only
read-only reentrancy is the worst class of bug because the contract passes every automated tool. you literally need a human to trace the external call flow
1031 ETH liquidated on Arbitrum alone. the attacker manipulated wstETH pricing and the vault just let it happen because Curve state was mid-transition
1,031 ETH liquidated on Arbitrum from a price feed manipulation. Curve pool integrations are becoming a systemic risk.
Pavel D. the Curve integration issue is what makes this systemic. every protocol building on top of Curve pools with their own balances is exposed to the same class of bug
Astrid Holm systemic risk from Curve integrations. every protocol building on top is exposed to the same bug class
1,031 ETH is brutal but dForce paused the vaults within an hour and posted a bounty. faster response than most CEXs manage
wei z dForce pausing in an hour is fast for DeFi but the 1031 ETH was already gone. response speed is good, prevention is better. they should have had a guard on the integration
Curve pool integrations are only risky if the consuming protocol doesnt add their own safeguards. dForce relied on Curve internal balances without a reentrancy guard of their own
exactly. curve itself was fine, dForce didnt add their own guard. protocols composing on top of composable protocols without extra guards is the pattern that keeps generating these
another day another defi exploit. at least dForce responded fast and paused the vaults
1031 ETH liquidated on Arbitrum alone. the attacker picked L2s because lower gas meant more iterations of the exploit for the same cost
1031 ETH from a read-only reentrancy on Arbitrum. L2 security tooling is years behind mainnet. teams deploying on optimism and arbitrum are running with less tooling than defi had in 2020
L2 tooling gap is real. ran slither and mythril on our arbitrum deployment and both missed cross-contract reentrancy that manual review caught in 20 minutes
read-only reentrancy passing every slither check is nightmare fuel. the tool says your contract is clean while the exploit vector is right there
dForce paused within an hour and offered a bounty. some CEXs take 6 hours to respond to a hot wallet drain. defi incident response has gotten legitimately better
3.6M from a read-only reentrancy. the curve integration pattern is everywhere in DeFi, how many protocols are sitting on the same bug without knowing it
Beth C. the scary part is how many protocols integrate Curve pools without their own reentrancy guard. you could audit 50 projects and find this bug in half of them
curve_watcher_ the real number is probably higher than half. ran audits on 12 Curve integrations last year and 7 of them had zero reentrancy guard on the consumer side