Odin Fun releases the 4th update on the attack incident, with eight fixes and accountability efforts moving forward in parallel

BTC-1,31%

Gate News update: On April 9, Odin Fun co-founder Bob Bodily posted on X that multiple lines of work related to the Odin Fun attack are currently being carried out in parallel: the platform is rolling back to the state before the attack occurred; efforts are underway to retrieve large amounts of cryptocurrency withdrawn from the platform after the attack; it is working with law enforcement agencies and exchanges to trace and freeze the attackers’ funds, and to prepare legal action; it is coordinating with other Bitcoin protocols that have also been affected by a third-party smart contract vulnerability; the vulnerability has been confirmed, fixed, validated, and deployed to production; a comprehensive third-party smart contract audit is underway; it is maintaining ongoing communication with the major community to strive for the best resolution; and it is jointly discussing with users the optimal path to restart the platform. Previously, on April 1, Odin Fun saw abnormal, large-scale sell-offs, mainly involving a small number of meme coins (such as BURRITO and CRYPTOBURG), followed by reports from multiple users that account balances were abnormal and that BTC and tokens were extracted abnormally.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments