On Friday and Saturday, a series of events unfolded as a 13-block chain reorganization occurred on the Litecoin network, effectively rewinding 32 minutes of network activity. This reorganization 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 since been issued, advising all users to upgrade due to important security updates. According to the Litecoin Foundation, the bug has been fully patched, and the network is now operating normally. However, an examination of the litecoin-project GitHub repository reveals that the consensus vulnerability was privately patched between March 19 and 26, approximately four weeks prior to the attack.
A separate denial-of-service vulnerability was also patched on the morning of April 25, with both fixes being 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 was unknown to defenders at the time of the attack. The commit history of Litecoin shows that the consensus vulnerability was known and patched privately a month before the exploit, but the fix had not been publicly disclosed or mandated for all mining pools. This created a window of opportunity where some miners were running the patched code, while others were still running the vulnerable version, and the attackers seemed to be aware of the difference.
Alex Shevchenko, CTO of NEAR Foundation's Aurora project, has raised similar concerns, pointing out that blockchain data indicates the attacker pre-funded a wallet 38 hours before the exploit through a Binance withdrawal. The destination address was already set up to swap LTC for ETH on a decentralized exchange. Shevchenko argues that the denial-of-service attack and the MWEB bug were separate components, with the DoS designed to take patched mining nodes offline, allowing the unpatched ones to form a chain that included the invalid transactions. The fact that the network automatically handled the 13-block reorganization once the DoS stopped suggests that enough hashrate was running updated code to eventually overpower the attack, but only after the unpatched fork had run for 32 minutes.
This incident highlights the differences in how attacks on various networks are handled, depending on how code maintainers and developers react to exploits. Newer chains with smaller, more centralized validator sets can coordinate upgrades quickly, while older proof-of-work networks like Litecoin and bitcoin rely on independent mining pools choosing when to upgrade, creating a window of vulnerability when a security patch needs to reach everyone before an attacker exploits the gap.