A series of events unfolded over the weekend as a result of a vulnerability in the Mimblewimble Extension Block protocol, leading to a 13-block chain reorganization. This reorganization effectively reversed roughly 32 minutes of network activity after an attacker exploited the vulnerability to carry out a denial-of-service attack against several major mining pools.
The invalid transactions were temporarily allowed to pass through nodes that had not been updated, but the network's longest valid chain eventually corrected them. In response, the Litecoin Core v0.21.5.4 was released, containing crucial security updates and advising all users to upgrade. According to the Litecoin Foundation, the bug has been fully patched and the network is now operating normally.
However, some researchers have raised concerns regarding the timeline of events, citing the public commit log from the litecoin-project GitHub repository, which indicates 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 commenced. A zero-day vulnerability refers to a security flaw that is unknown to defenders at the time of an attack. The Litecoin commit history reveals 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, creating a window of vulnerability.
This window allowed the attackers to target specific mining pools, taking advantage of the fact that some miners were running the patched code while others were still using the vulnerable version. Concerns have been raised by experts such as Alex Shevchenko, CTO of NEAR Foundation's Aurora project, who pointed out that the denial-of-service attack and the MWEB bug were separate components, with the DoS designed to take patched mining nodes offline so that the unpatched ones would form the chain that included the invalid transactions. Blockchain data showed that the attacker had pre-funded a wallet 38 hours before the exploit through a Binance withdrawal, with the destination address already configured to swap LTC into ETH on a decentralized exchange. The automatic handling of the 13-block reorganization by the network 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 code maintainers and developers react to exploits on various networks. Newer chains with smaller, more centralized validator sets can coordinate upgrades and push patches network-wide in a matter of hours.
In contrast, older proof-of-work networks like Litecoin and bitcoin rely on independent mining pools choosing when to upgrade, which can create 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.