Injective Mainnet Halts for Nearly 4 Hours, Attackers Steal $4.88M

iconKuCoinFlash
Share
This is the logo of the coin.
ETH
$2,506.934.34%
AI summary iconSummary
On-chain reports indicate that the Injective mainnet halted block production for nearly four hours on August 31, with blockchain height resuming from 181,027,006 to 181,027,007. No rollback occurred, and QuickNode confirmed a network-wide stall. An emergency patch was deployed. On-chain analyst Rarma noted that attackers exploited the insurance fund and binary options market, executing 299 transactions and siphoning 1,979.8 ETH ($4.88M) to a single address. The incident underscores the need for a network upgrade to prevent future exploits.

BlockBeats news, on September 1, according to on-chain researcher Rarma’s analysis, Injective halted block production for approximately 3 hours and 42 minutes on August 31, with the block height recovering from 181,027,006 to 181,027,007 without any rollback. QuickNode’s status logs also confirmed a complete network block stagnation on Injective’s mainnet that day, followed by the deployment of an emergency patch.


The attacker allegedly exploited Injective’s insurance fund and its permissionless binary options market mechanism repeatedly, executing 299 related operations and ultimately consolidating approximately 1,979.8 ETH—valued at around $4.88 million—into a single address.

Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.