A 13-block chain reorganization on late Friday and Saturday rewound roughly 32 minutes of community exercise after attackers used a vulnerability in its Mimblewimble Extension Block (MWEB) protocol.
The bug had enabled a denial-of-service assault in opposition to main mining swimming pools, permitting the invalid MWEB transactions to slide by means of nodes that had not up to date, earlier than the community’s longest legitimate chain corrected them.
The Foundation stated in Asian morning hours on Sunday the bug was totally patched and the community is working usually.
However, distinguished researchers say the litecoin-project GitHub repository tells a completely different story. Security researcher bbsz, who works with the SEAL911 emergency response group for crypto exploits, posted the patch timeline pulled from the general public commit log.
Now that stuff has been made public on the Litecoin GitHub, we’ve a higher sense of timeline and what occurred.
In the age of Mythos, this timeline merely would not fly.
The autopsy says one zero-day induced a DoS that allow an invalid MWEB tx slip by means of. The git go browsing… https://t.co/zMMrheQLPP pic.twitter.com/O3DtdwV0rF
— bbsz (@blackbigswan) April 26, 2026
The consensus vulnerability that allowed the invalid MWEB peg-out was privately patched between March 19 and March 26, roughly 4 weeks earlier than the assault. A separate denial-of-service vulnerability was patched on the morning of April 25.
Both fixes have been rolled into launch 0.21.5.4 the identical afternoon, after the assault had already begun.
“The post-mortem says one zero-day caused a DoS that let an invalid MWEB transaction slip through,” bbsz wrote. “The git log tells a slightly different story.”
A zero-day refers to a vulnerability unknown to defenders on the time of an assault.
Litecoin’s commit history shows the consensus vulnerability was recognized and patched privately a month earlier than the exploit, however the repair had not been broadcast publicly or required to all mining swimming pools.
That created a window the place some miners ran the patched code whereas others ran the still-vulnerable model, and the attackers seem to have recognized which was which.
Alex Shevchenko, CTO of NEAR Foundation’s Aurora venture, raised parallel concerns in a thread.
Blockchain knowledge confirmed the attacker pre-funded a pockets 38 hours earlier than the exploit by means of a Binance withdrawal, with the vacation spot handle already configured to swap LTC into ETH on a decentralized change.
The denial-of-service assault and the MWEB bug have been separate elements, Shevchenko argued, with the DoS designed to take patched mining nodes offline so the unpatched ones would type the chain that included the invalid transactions.
The undeniable fact that the community routinely dealt with the 13-block reorganization as soon as the DoS stopped suggests sufficient hashrate was working up to date code to finally overpower the assault, however solely after the unpatched fork had run for 32 minutes.
Successful on Litecoin shows how assaults on varied networks differ in how code maintainers and builders react to exploits. Newer chains with smaller, extra centralized validator units coordinate upgrades by means of discussion groups and may push patches network-wide in hours.
Older proof-of-work networks like Litecoin and bitcoin depend on unbiased mining swimming pools selecting when to improve, which works for non-urgent adjustments however creates a window of vulnerability when a safety patch wants to succeed in everybody earlier than an attacker exploits the hole.
The Litecoin Foundation has not publicly addressed the GitHub timeline as of Sunday morning.
The quantity of LTC pegged out through the invalid block window and the worth of any swaps accomplished earlier than the reorganization reversed them haven’t been disclosed.
