On Friday and Saturday, a series of events unfolded as a 13-block chain reorganization on the Litecoin network occurred, effectively rewinding 32 minutes of network activity. This was in response to a denial-of-service attack that exploited a vulnerability in the Mimblewimble Extension Block (MWEB) protocol, allowing invalid transactions to bypass nodes that had not been updated. The Litecoin Core v0.21.5.4 release has been issued, advising all users to upgrade due to important security updates. According to the Litecoin Foundation, the bug was fully patched, and the network is now operating normally.
However, a review of the litecoin-project GitHub repository by security researchers reveals a different timeline. The consensus vulnerability that allowed the invalid MWEB peg-out was known and privately patched between March 19 and March 26, roughly four weeks before the attack. A separate denial-of-service vulnerability was patched on the morning of April 25, with both fixes rolled into the release 0.21.5.4 the same afternoon, after the attack had begun.
The term 'zero-day' refers to a vulnerability that is unknown to defenders at the time of an attack. In this case, the consensus vulnerability was known and patched privately a month before the exploit but not publicly disclosed or mandated for all mining pools, creating a window of vulnerability. Alex Shevchenko, CTO of NEAR Foundation's Aurora project, highlighted concerns that the denial-of-service attack and the MWEB bug were separate components, with the DoS designed to take patched mining nodes offline, allowing unpatched ones to form a chain that included invalid transactions. Blockchain data indicated that the attacker pre-funded a wallet 38 hours before the exploit and had configured the destination address to swap LTC into ETH on a decentralized exchange.
The network's automatic handling of the 13-block reorganization once the DoS stopped suggests that enough hashrate was running updated code to eventually overpower the attack. This incident highlights the differences in how code maintainers and developers react to exploits across various networks.
While newer chains can coordinate upgrades quickly, older proof-of-work networks like Litecoin and Bitcoin rely on independent mining pools choosing when to upgrade, creating a window of vulnerability for security patches. The Litecoin Foundation has not publicly addressed the GitHub timeline as of Sunday morning, and the amount of LTC pegged out during the invalid block window and the value of any swaps completed before the reorganization reversed them have not been disclosed.