Based on Bijiie, Flow blockchain validators have implemented a protocol fix (Mainnet 28) following a security vulnerability that led to the theft of approximately $3.9 million in assets via a cross-chain bridge. The attack occurred on December 27, with the network being shut down to prevent further unauthorized transactions. The vulnerability has been isolated, law enforcement has been notified, and user funds prior to the incident remain intact. Validators have restored the network to its pre-attack state and relaunched it in read-only mode. Ecosystem partners are synchronizing the system, and transactions remain paused pending final coordination. The network is expected to fully reopen after a technical analysis planned within 72 hours.
Flow Blockchain Deploys Protocol Fix After $3.9M Security Breach
币界网Share
Summary
Flow blockchain validators rolled out a protocol update following a security breach that saw $3.9 million stolen through a cross-chain bridge. The incident occurred on December 27, prompting a network shutdown to block further unauthorized transactions. The vulnerability has been isolated, and authorities have been alerted. Validators restored the network to its pre-attack state and relaunched it in read-only mode. Ecosystem partners are syncing the system, with transactions paused until coordination is complete. A full reopening is expected after a 72-hour technical review.
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.