Based on Ether Leeum, the RWA protocol ZOTH was the second hacked for $ 880 million a month.

ZOTH, a platform based on Ether Leeum, which focuses on tokenized real assets, suffered a second major violence within three weeks on March 21, and the attackers produced $ 88.5 million in digital assets.

The company is checking the violation and working with a security expert to investigate the case.

ZOTH also provides $ 500,000 of the $ 500,000 bounty, leading to the identification of hackers in charge of abuse of $ 880 million.

The hacks that occurred at the beginning of March 21 were included in the attacker compromise the manager key and control the ZOTH proxy contract. The hacker has upgraded the contract to enable the transfer of unauthorized funds.

According to the onChain analysis, $ 880 million in USD0 ++ Stablecoins was drained from the contract and converted to 4,223 ETH and later moved to an external wallet.

ZOTH ensures that there is a step to recognize security violations and alleviate the influence on users. The company promised to announce the entire report when the investigation was completed.

Second hack

This is the second abuse for ZOTH this month. On March 6, the attacker exploited vulnerability in one of the liquidity pools, completing the synthetic assets without sufficient collateral and causing $ 285,000 loss.

Security experts suggest that violations can be prevented by better major management and real -time monitoring. It warns that other contracts in the platform shares the same administrator access, which can lead to risks.

ZOTH did not disclose whether it would be repaid to the affected users, but he said he is doing his best to strengthen security measures to prevent future cases.

This event emphasizes the continuous danger facing the risk of dependent on the dispersed financial platform, especially the centralized manager control. Blockchain security firms have shown that elaborate major compromises have increased due to more than $ 10 billion in defect -related exploit for the past five years.

The company did not mention how the attacker got a private key, but promised to provide an update after the investigation.