In the years I’ve spent working on iPad as my primary computer, I’ve learned to appreciate the platform’s advantages over the Mac (a richer app ecosystem and superior modularity, for instance), and I’ve accepted its limitations. If you enjoy my content and want to show your support, please like, share, and follow me for more high-quality updates.Yoink’s new persistent clipboard monitoring. I'm passionate about providing you with the latest insights and analysis on the world of cryptocurrencies. It is essential to stay vigilant and practice safe trading habits to prevent loss of funds due to cyberattacks. SushiSwap Head Chef Jared Grey's recommendation to revoke the RouterProcessor2 contract on all chains is crucial to prevent similar attacks from happening in the future. SushiSwap's recent exploit highlights the importance of taking necessary precautions when using DeFi platforms.
Response from SushiSwap Head Chef Jared Grey:
However, more than 2000 addresses on Layer 2 Arbitrum have seemingly approved the bad contract. The Block Research Analyst Kevin Peng reveals that so far, 190 Ethereum addresses have approved the problematic contract. DeFi Llama's has published a list of contracts across all chains that should be revoked, and they built a tool to check if any of your addresses have been impacted. Following the first attack for 100 ETH, another hacker came along and stole another 1800-ish ETH using the same contract but named their function "notyoink." How Many Users are Affected?Įarly reports suggest that not many SushiSwap users are at risk, with only those who swapped on the platform within the last four days being affected. The exploit allows an unauthorized entity to "yoink" tokens without proper approval from the token owner. The attack vector is a bug in the "approve" mechanism of the SushiSwap router contract. Later on in the swap3callback function, the permission check gets bypassed, allowing an unauthorized entity to steal tokens from users who have unknowingly approved the bad contract. This function calls swapUniV3() to set variable "lastCalledPool," which is at storage slot 0x00. The root cause, according to Ancilia, Inc., is due to a bug in the internal swap() function. The attack involved an approve-related bug on the RouterProcessor2 contract, prompting SushiSwap Head Chef Jared Grey to recommend revoking it on all chains. Response from SushiSwap Head Chef Jared Greyĭecentralized exchange SushiSwap was hit by an exploit that led to the loss of more than $3.3 million from at least one user.SushiSwap Hack: More than $3.3M Lost, Head Chef Recommends Revoking RouterProcessor2 Contract We will Cover this in This Article 👇 Response from SushiSwap Head Chef Jared Grey:.SushiSwap Hack: More than $3.3M Lost, Head Chef Recommends Revoking RouterProcessor2 Contract.
0 kommentar(er)
