On Friday and Saturday, the Litecoin network experienced a 13-block chain reorganization, effectively reversing 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 temporarily pass through unupdated nodes. The Litecoin Core v0.21.5.4 release contains crucial security updates and users are advised to upgrade.
According to the Litecoin Foundation, the bug has been fully patched and the network is now operating normally. However, security researchers point out that the timeline of events, as indicated by the litecoin-project GitHub repository, suggests the consensus vulnerability was privately patched between March 19 and 26, more than four weeks before the attack occurred.
This raises questions about the handling of the vulnerability and the subsequent attack. The vulnerability allowed for a denial-of-service attack against major mining pools, enabling the invalid MWEB transactions to slip through before the network's longest valid chain corrected them. Prominent researchers, including bbsz from the SEAL911 emergency response group for crypto exploits, have analyzed the public commit log and posted the patch timeline. This has provided a clearer understanding of the timeline and the events that transpired.
Furthermore, the researcher argues that the post-mortem account of a single zero-day causing a DoS that let an invalid MWEB transaction slip through does not align with the actual timeline. A separate denial-of-service vulnerability was patched on the morning of April 25, and both fixes were included in 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 indicates that the consensus vulnerability was known and patched privately a month before the exploit but had not been publicly disclosed or mandated for all mining pools.
This created a window of opportunity for attackers, who appeared to be aware of which miners were running the patched code and which were still vulnerable. Alex Shevchenko, CTO of NEAR Foundation's Aurora project, has raised parallel concerns and pointed out that blockchain data showed the attacker pre-funded a wallet 38 hours before the exploit through a Binance withdrawal.
The destination address was already configured to swap LTC into ETH on a decentralized exchange. Shevchenko argued that the denial-of-service attack and the MWEB bug were separate components, with the DoS designed to take patched mining nodes offline so the unpatched ones would form the 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 how attacks on various networks differ in 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. As of Sunday morning, the Litecoin Foundation has not publicly addressed the GitHub timeline. 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.