The attacker, who hacked the decentralized finance (DeFi) yield farming protocol Harvest Finance on Monday and exploited $34 million worth of funds, is still out there. Harvest Finance is continuously trying to retrieve its funds back from the attacker but is unable to get any information on him. It even offered community members a bounty of $100k for reaching out to the attacker but didn’t get anything of it.
Now, Harvest Finance has increased its bounty from $100,000 to $1 million for tracking down the attacker and helping the platform in retrieving stolen funds. The protocol will provide this massive amount to the person or the team who will provide certain information about the attacker that may lead to the stolen funds. Before offering $1 million, it offered $400,000 as a bounty reward.
Shortly after the attack, Harvest Finance was able to come up with some information regarding the hacker. The team behind the yield farming protocol said that they have got a “significant amount of personally identifiable information” on the respective hacker. Also, it said that the attacker is very famous in the cryptocurrency community.
Now, Harvest Finance has said in a tweet that they do not possess any direct hard proof. Therefore, they are offering a bounty of $1 million to people so that they may provide key information on the hacker. The main point of this huge bounty is to get “the direct hard proof leading to the return of funds”, the DeFi protocol said. The platform has not got any other plan for reaching out to the attacker other than this.
Harvest Finance was attacked on Monday, October 26, 2020, in which it lost $34 million worth of stablecoins. Reportedly, the hack was performed on Curve y pool by the hacker who converted the stolen Farm USDT and Farm USDC tokens into renBTC and then into Bitcoin. Only $2.5 million was sent back to the deployer account and all of the remaining amount is still in the custody of the attacker.
While explaining this attack, later on, Harvest Finance said that it was an “engineering error” that led to this exploit.