Decentralized U.S. greenback stablecoin protocol Raft claims that regardless of a number of safety audits, the agency nonetheless suffered a safety exploit resulting in the lack of $6.7 million final week.
Based on the challenge’s Nov. 13 autopsy report, a number of days prior, a hacker borrowed 6,000 Coinbase-wrapped staked Ether (cbETH) on decentralized finance protocol Aave, transferred the sum to Raft, and minted 6.7 million Raft stablecoin, dubbed “R,” utilizing a sensible contract glitch.
The unauthorized minted funds have been then swapped off the platform via liquidity swimming pools on decentralized exchanges Balancer and Uniswap, netting $3.6 million in proceeds. The R stablecoin depegged after the assault.
Based on the report:
“The first root trigger was a precision calculation situation when minting share tokens, which enabled the exploiter to acquire additional share tokens. The attacker leveraged the amplified index worth to extend the value of their shares.”
The good contracts exploited in the course of the incident have been audited by blockchain safety companies Path of Bits and Hats Finance. “Sadly, the vulnerabilities that led to the incident weren’t detected in these audits,” Raft builders wrote.
The challenge says that because the Nov. 10 incident it has filed a police report and is at present working with centralized exchanges to trace down the circulate of the stolen funds. All Raft’s good contracts are at present suspended, although customers who minted R “retain the flexibility to repay their positions and retrieve their collateral.”
Decentralized stablecoins are minted utilizing customers’ crypto deposits as collateral. Final December, decentralized stablecoin HAY depegged towards the U.S. greenback after a hacker took advantage of a smart contract glitch and minted 16 million HAY with out correct collateral. The HAY stablecoin has since re-pegged, partly, because of the protocol requiring a collateralization ratio of 152% on the time of exploit as a part of threat administration.
We’re conscious of a possible safety vulnerability.
We’re at present investigating and can present an replace as quickly as we are able to.
— Raft (@raft_fi) November 10, 2023