MENU

Coinler

Borsalar

Bitcoin (BTC)
$ 72,084.86 2,580.96 (% 3.71)
Ethereum (ETH)
$ 4,038.91 133.93 (% 3.43)
XRP (XRP)
$ 0.727106 0.113616 (% 18.52)
Binance Coin (BNB)
$ 519.52 -11.81 (% -2.22)
Tether (USDT)
$ 1.00 0 (% -0.12)
Litecoin (LTC)
$ 105.01 16.80 (% 19.04)
Cardano (ADA)
$ 0.774866 0.057416 (% 8.00)
Bitcoin Cash (BCH)
$ 443.57 17.63 (% 4.14)
Ethereum Classic (ETC)
$ 37.783474 1.333105 (% 3.66)
Stellar (XLM)
$ 0.15958 0.01918 (% 13.66)
Cosmos (ATOM)
$ 13.68 0.54 (% 4.14)
EOS (EOS)
$ 1.24 0.09 (% 8.19)
TRON
$ 0.133004 -0.001235 (% -0.92)
Tezos (XTZ)
$ 1.508825 0.086660 (% 6.09)
NEO (NEO)
$ 18.02 1.05 (% 6.18)
Dash (DASH)
$ 43.44 3.21 (% 7.99)
Holo (HOLO)
$ 0.003539 0.000008 (% 0.23)
Basic Attention Token (BAT)
$ 0.218578 -0.000524 (% -0.24)

Exploit Involving Early Version Of Yearn Finance Saw Damages Of $11.6 Million: PeckShield

It appears to involve a misconfigured token created by an early version of Yearn Finance.

Exploit Involving Early Version Of Yearn Finance Saw Damages Of $11.6 Million: PeckShield

An exploit involving an early version of the DeFi protocol Yearn Finance, called iearn, took place earlier today, causing damages of $11.6 million, according to PeckShield.

The exploiter received a mix of stablecoins, including DAI, USDC, BUSD, TUSD and USDT, according to LookOnChain.

Pseudonymous crypto researcher Samczsun claimed that Yearn Finance's version of USDT, called yUSDT, has been broken since it was deployed around three years ago. He said it was "misconfigured to use the Fulcrum iUSDC token instead of the Fulcrum iUSDT token."

PeckShield corroborated this idea. It said that the root cause appears to be the misconfigured yUSDT. This was exploited to mint 1.2 quadrillion yUSDT from just $10,000. This was then cashed out by swapping to other stablecoins.

"We are aware of an issue that seems isolated to the iearn legacy protocol launched in 2020 and liquidity pool," said Yearn Finance contributor Storm Blessed 0x on Twitter. "Yearn v2 vaults seem not to be impacted. Yearn contributors are investigating."

By signing-up you agree to our Terms of Service and Privacy Policy

The attack used the Aave V1 protocol in making a large array of swaps but the Aave team said that it wasn't exploited.

"We can confirm that Aave V1 was not impacted," said Aave CEO Stani Kulechov on Twitter.

"We need to clarify that the root cause is due to misconfigured yUSDT, not related to Aave," added PeckShield.

 

Soure: theblock.co