link.png

ID:

vesper-finance-1148

Date:

Status:

Incident Count:

March 16, 2021

Near-Miss

3

info.png
target.png
REKT

Contributor:

chain.png

web3rekt.com

KYC By:

KYC:

None

info.png

Audit By:

Audits:

CoinInspect, DeFiSafety

Loss Amount:

-

info.png

Recovered:

-

Rewards:

-

Currency:

USD

info.png

Key Indicators

Platform:

Type:

Category:

Method:

Data Sources:

Ethereum

Protocol

Dexes

Rewards - Bug Bounties

Extended Method:

A malicious user could have stolen the yield generated by Vesper’s strategies through intercepting the rebalance swap from the WETH/VSP pool on Uniswap.

info.png

Days in Operation:

759

(2.08 Years)

chain.png
chain.png
chain.png
chain.png
datasource.png

The Dedaub Team, led by Yannis Smaragdakis and Neville Grech, requested disclosure assistance from Immunefi for a vulnerability found in the bluechip DeFi project Vesper on March 16. The maximum funds at risk historically appears to have been 78.6 ETH, a third of which would have gone to fees as part of the attack. This vulnerability was never exploited by any malicious actors, and Vesper quickly introduced a fix. No original user funds were at risk, since the exploit targeted yields. Following the disclosure and fix, Vesper is joining Immunefi with a smart contract bug bounty for $200,000 and engaging Dedaub for an audit of Vesper contracts.

Vesper has paid out an undisclosed bounty to the Dedaub Team and thanks Immunefi for helping to facilitate disclosure assistance.

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.