A hacker who stole $1 million in cryptocurrency from Sentiment’s decentralized finance protocol has returned 90% of the money. Through Twitter, Sentiment has acknowledged receiving the payments.
It has taken Sentiment, an arbitrum- based DeFi lending and borrowing platform, just 48 hours to recover 90% of the stolen funds after being attacked by reentrancy hackers who stole nearly $1 million in altcoins.
On April 5, Sentiment offered a $95,000 bounty to the attacker or anyone with valuable information about the incident, and gave those who were responsible a two-day deadline to return the stolen funds.
Read More: Sentiment DeFi Platform Lost $1 Million To A Hacker On Arbitrum
On April 6, the attacker returned the stolen funds to a wallet address under the custody of the Sentiment project. Additionally, the DeFi platform verifies receiving nearly all of the stolen funds.
#CertiKSkynetAlert 🚨
Sentiment exploiter 0xdd0 has sent ~$477.1k (250 ETH) to wallet 0xc5f that is believed to be controlled by the @sentimentxyz team
Yesterday, 0xc5f sent a message to the Sentiment exploiter outlining a $95K reward if the assets are returned
Stay safe! pic.twitter.com/swPBmr73ST
— CertiK Alert (@CertiKAlert) April 5, 2023
Through numerous types of hacks, rug pulls, and scams, perpetrators successfully stole over $3 billion from the crypto space in 2022. In just the first three months of this year, crypto criminals have stolen over $100 million.Â
In contrast to the previous year, however, the success rate of bounty negotiations between hackers and projects has increased dramatically.
Earlier this week, following a successful bounty negotiation, Euler Finance, which experienced a nearly $200 million flash loan attack in March, recovered 90% of the stolen funds.
Similarly, on April 4, it was reported that the hacker responsible for the $573,000 Allbridge attack had accepted a ‘white hat reward’ in exchange for the stolen crypto assets.Â
Recommended:
Euler Labs Hacker Returns “All Recoverable Funds” From The $200M Euler Finance Hack
Discussion about this post