White Hacker Returns $5.4M To Curve Finance Protocol After The Exploit
- The MEV Bot deployer returned $5.4 million worth of ETH to Curve Finance voluntarily, helping to mitigate the damages caused by the exploit.
- Curve Finance suffered a $52 million loss due to an attack caused by a Vyper recursive lock failure affecting certain versions of the Ethereum programming language.
- DeFi protocols, including Alchemix, are taking precautionary measures after the vulnerability was discovered.
In a recent incident, the decentralized finance (DeFi) protocol Curve Finance faced an attack that resulted in a loss of $52 million from its stablecoin pool alETH/msETH/pETH. The attack was attributed to a vulnerability found in certain versions of Vyper, an Ethereum Virtual Machine (EVM) contract programming language.
The exploit, caused by a Vyper recursive lock failure, affected versions 0.2.15, 0.2.16, and 0.3.0 of the language. Due to this critical vulnerability, various DeFi protocols have been subjected to a stress test as security agencies are closely monitoring the situation.
During the attack, multiple liquidity pools on Curve Finance, including aETH/ETH, msETH/ETH, pETH/ETH, and CRV/ETH, were targeted by the attackers. The malicious actors managed to drain these pools entirely using the reentrancy lock flaw. Curve Finance confirmed that all other remaining pools remained unaffected and secure.
Prompt action was taken by Curve Finance following the attack. The early deployer of the “MEV Bot,” identified as c0ffeebabe.eth, voluntarily returned 2,879.54 ETH, valued at approximately $5.4 million, to the Curve Finance deployer. This gesture demonstrated an effort to mitigate the damages caused by the exploit.
The incident has prompted discussions within the DeFi community regarding the safety and security of smart contracts. Vyper’s official documentation was found to recommend the wrong version for installation, contributing to the vulnerability exploited by the attackers.
One of the affected projects, Alchemix, took swift action upon receiving a notice from Curve Finance about the attack on the alETH/ETH pool due to a Vyper error. Alchemix quickly initiated a process to remove AMO (Alchemix’s proprietary token) from the Curve pool through the AMO contract’s control mobility. It is essential to note that the Alchemix smart contract itself remained uncompromised, ensuring the safety of users’ funds.
However, the alETH/ETH Curve pool suffered a loss of approximately 5,000 ETH during the process of removing the remaining liquidity controlled by AMO. As a result, Alchemix advised its users to refrain from providing liquidity in the alETH/ETH Curve pool. While providing liquidity for alETH elsewhere may be technically safe, users must remain cautious, as attackers might exploit the liquidity for their benefit.
The incident highlights the significance of diligent security audits and the need for continuous monitoring and updates in the fast-evolving DeFi landscape. Developers and users are urged to be vigilant and take necessary precautions to safeguard against potential exploits in DeFi protocols.
In response to the incident, the developers behind Vyper have announced that the recursive locks of the affected versions, 0.2.15, 0.2.16, and 0.3.0, are now considered invalid. This action is aimed at preventing further incidents arising from the same vulnerability in other protocols that rely on Vyper for their smart contracts.
As Coincu reported, Aave accepted an urgent motion to deactivate CRV borrowing on Ethereum. The prohibition is intended to prevent traders from abusing Curve flaws and indulging in malicious shorting of borrowed CRV, which might result in repeated liquidations.
DISCLAIMER: The information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your own research before investing.