Aethir Successfully Thwarts an ATH Token Cross-Chain Bridge Attack, with User Losses Below $90k

ATH-1,22%
ETH0,8%
ARB5%

Gate News message, April 10, Aethir today released a security alert stating that the team has monitored and successfully contained a malicious attack on the ATH token cross-chain bridge contract. After the incident, all affected contracts were quickly disconnected, and the related vulnerabilities have also been effectively controlled. The core ATH token circulating supply on the Ethereum mainnet remains intact and unaffected, and the ETH-ARB cross-chain bridge on Squid was likewise not involved. This security incident has had a relatively limited overall impact on users, with total losses of less than $90k. Aethir said that a complete compensation plan will be published next week; it is currently actively working with multiple exchanges and law enforcement agencies to advance the freezing of relevant funds and the tracking of the attacker. Aethir emphasized that it will remain fully transparent and will continue to provide the community with updates on the incident’s progress. With further monitoring of the relevant funds, a complete list of the attacker’s wallets will be published through the official Discord community, along with a detailed report that will disclose the sequence of events, the scope of affected users, and the compensation mechanism.

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