top of page
link.png

ID:

lendf-me-529

blob_404.png

Date:

Status:

Incident Count:

April 19, 2020

Verified

2

info.png
REKT

Contributor:

chain.png

zerofriction.io

KYC By:

KYC:

None

info.png
50 pts

Audit By:

Audits:

None

Loss Amount:

25,236,849

info.png

Recovered:

-

Rewards:

Ticker:

USD, imBTC

info.png
100 pts
info.png

Platform:

Type:

Category:

Method:

Data Sources:

Ethereum

Protocol

Dexes

Contract Vulnerabilities

Extended Method:

Reentrancy attack

Days in Operation:

0

chain.png
chain.png
chain.png
chain.png
datasource.png
100 pts each

A known reentrancy vulnerability was exploited on Uniswap against the imBTC. liquidity pool. Around 24 hours later, at Apr-19–2020 12:58:43 AM +UTC, a similar hack occurred on Lendf.Me.” reads the analysis published by Blockchain security firm PeckShield. “Technically, the main logic behind these two incidents is the fact that the implementation of ERC777-compatible transferFrom() has a callback mechanism, which allows the attacker to utterly hijack the transaction and perform additional illicit operations (via _callTokensToSend()) before the balance is really updated (i.e., inside _move()). In the case of the Lendf.Me hack, the attacker exploited the same issue to increase the internal record of the attacker’s imBTC collateral amount so that she can borrow (and indeed borrow) a variety of 10+ assets from all available Lendf.Me liquidity pools (with total asset value of $25,236,849.44).

info.png

DISCLAIMER: While web3rekt has used the best efforts in aggregating and maintaining this database, this web site makes no representations or warranties with respect to the accuracy or completeness of its information and data herein, and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose. 

Under no circumstances, shall web3rekt be liable for any loss of profit or funds, any regulatory or governmental penalties, any legal costs, or any other commercial and non-commercial damages, including but not limited to special, incidental, consequential, or other damages from any or all usage of the data and information derived from this database.

bottom of page