A recent chain reorganization on the Litecoin network, affecting 13 blocks and approximately 32 minutes of activity, was caused by an exploit of a vulnerability in the Mimblewimble Extension Block (MWEB) protocol. The bug allowed for a denial-of-service attack against major mining pools, enabling invalid MWEB transactions to bypass nodes that had not been updated, before the network's longest valid chain corrected them. Following the incident, Litecoin Core v0.21.5.4 was released, containing crucial security updates.

According to the Litecoin Foundation, the bug was fully patched and the network is now operating normally. However, security researchers argue that the timeline of events, as revealed by the litecoin-project GitHub repository, contradicts the 'zero-day' attack claim.

The repository shows that the consensus vulnerability was privately patched between March 19 and 26, roughly four weeks prior to the attack. A separate denial-of-service vulnerability was patched on the morning of April 25, with both fixes being rolled into release 0.21.5.4 the same afternoon, after the attack had begun. The fact that the vulnerability was known and patched a month before the exploit, yet not publicly disclosed or mandated for all mining pools, created a window of opportunity for the attackers.

They appeared to be aware of which miners were running the patched code and which were still vulnerable. Blockchain data revealed that the attacker had pre-funded a wallet 38 hours before the exploit, with the destination address already set to swap LTC for ETH on a decentralized exchange. 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 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 on various networks. While newer chains with smaller, more centralized validator sets 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 when a security patch needs to reach everyone before an attacker exploits the gap.