Key Insights
- A 13-block reorg on Litecoin led to an exploit that has been taken under control.
- Multichain platforms were briefly susceptible to invalid MWEB peg-out transactions.
- The exploit raises risks with legacy blockchains
Litecoin has experienced a network fork as the result of a zero-day attack on its MimbleWimble Extension Block (MWEB) protocol. Older nodes were able to mine a bad transaction, forking the blockchain for more than 3hours. The attack led to the creation of a new blockchain affecting the consensus of transactions.
The attack was created by the bad actor creating a transaction that was valid for older versions, but not the latest versions. This enabled invalid peg-outs, where coins were pegged-out to other decentralized exchanges. The fork was not able to reach consensus until the main chain was restored.
Litecoin Reorg Eliminates Invalid Transactions
The Litecoin development team identified the problem with the blocks 3,095,930 to 3,095,943. The attack was fixed with a 13-block reorganisation of the Litecoin blockchain, removing invalid transactions and putting back the correct history. The attack did not affect transactions that were valid.
The longer block generation time was an indicator of some network anomaly, as it took more than 32 minutes to generate blocks. Some people suspected this attack to be a 51% attack, but it was later confirmed that it was corrective. This showed that Litecoin’s consensus protocol was functioning.
Distributed Attack Allows Double Spend Attack
During the fork, hackers attempted to exploit the inconsistencies by creating double-spend attacks on cross-chain swap systems. These accepted MWEB peg-outs that were subsequently rejected by the recovery. This left some decentralized applications open to double-spend attacks.
Alex Shevchenko, CEO of Aurora Labs, said the attack was deliberate and put the potential loss for NEAR Intents at $600,000. He also advised exchanges to be vigilant in inspecting Litecoin balances and transactions due to the rise in potentially fraudulent double-spends. The attack raises concerns about the risks of cross-chain transactions in a period of network instability.
The attack highlights problems with legacy blockchain.
And Litecoin experienced an unusual blockchain fork due to a zero-day exploit in its MimbleWimble Extension Block protocol. The attack allowed old mining nodes to process an invalid transaction, resulting in a blockchain fork that occurred for over three hours. This created a forked blockchain, which can impact the security and consensus of the network.
The hackers started the attack by mining a transaction that was valid for old nodes but not new nodes. This decline was while the cryptocurrency market was on a generalised upward trajectory. The low reaction suggests that the market viewed the attack as an isolated one, but it added to a sense of caution.
Security Patch On Network Inspires Confidence
The Litecoin Foundation noted the vulnerability has been fixed and such attacks will not be possible in the current system. While the foundation did not disclose the number of attempted fraudulent transactions, it said that the system is now running smoothly. The patching went a long way to reassuring users and developers.
The attack is the first major one on the MWEB privacy feature since it was turned on in May 2022. Although this feature is being widely adopted, the attack demonstrates the importance of modern mining equipment. And it highlights the ever-present issues in the security of a dynamic environment.
Conclusion
Litecoin’s successful recovery from an involved attack through a successful reorganisation of the blockchain demonstrates the resilience of the network to both survive and preserve valuable transactions. The attack demonstrated the need to update non-updated nodes. There was little financial damage but the attack shows risks in mature networks. Ultimately, trust will be built via better security and technology.
FAQs
1. Why is Litecoin down?
It was a zero-day vulnerability in the MWEB protocol of older mining nodes.
2. Was there any loss?
No, there were no losses as the invalid transactions are rolled back in the chain reorganization.
3. What does chain reorganization mean?
In a chain reorganization, we take the invalid blocks out and replace it with valid blocks to revert to the valid chain.
4. How was the attack done?
The hackers created invalid transactions that were valid with a previous version of the code and was able to do an invalid peg-out.
5. Is the problem fixed?
Yes, the Litecoin Foundation has said the bug has been fixed and it is safe
