A 13-block chain reorganization on late Friday and Saturday rewound roughly 32 minutes of network activity after attackers used a vulnerability in its Mimblewimble Extension Block (MWEB) protocol.
The bug had enabled a denial-of-service attack against major mining pools, allowing the invalid MWEB transactions to slip through nodes that had not updated, before the network’s longest valid chain corrected them.
The Foundation said in Asian morning hours on Sunday the bug was fully patched and the network is operating normally.
However, prominent researchers say the litecoin-project GitHub repository tells a different story. Security researcher bbsz, who works with the SEAL911 emergency response group for crypto exploits, posted the patch timeline pulled from the public commit log.
Now that stuff has been made public on the Litecoin GitHub, we have a better sense of timeline and what happened.
In the age of Mythos, this timeline simply doesn’t fly.
The post-mortem says one zero-day caused a DoS that let an invalid MWEB tx slip through. The git log on… 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 four weeks before the attack. A separate denial-of-service vulnerability was patched on the morning of April 25.
Both fixes were rolled into release 0.21.5.4 the same afternoon, after the attack 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 at the time of an attack.
Litecoin’s commit history shows the consensus vulnerability was known and patched privately a month before the exploit, but the fix had not been broadcast publicly or required to all mining pools.
That created a window where some miners ran the patched code while others ran the still-vulnerable version, and the attackers appear to have known which was which.
Alex Shevchenko, CTO of NEAR Foundation’s Aurora project, raised parallel concerns in a thread.
Blockchain data showed the attacker 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 denial-of-service attack and the MWEB bug were separate components, Shevchenko argued, 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 enough hashrate was running updated code to eventually overpower the attack, but only after the unpatched fork had run for 32 minutes.
A hit on Litecoin shows how attacks on various networks differ in how code maintainers and developers react to exploits. Newer chains with smaller, more centralized validator sets coordinate upgrades through chat groups and can push patches network-wide in hours.
Older proof-of-work networks like Litecoin and bitcoin rely on independent mining pools choosing when to upgrade, which works for non-urgent changes but creates a window of vulnerability when a security patch needs to reach everyone before an attacker exploits the gap.
The Litecoin Foundation has not publicly addressed the GitHub timeline as of Sunday morning.
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.