Attackers Exploit Litecoin MWEB Zero-Day, Trigger 13-Block Reorganization and DoS on Mining Pools

Litecoin suffered a denial-of-service attack after attackers exploited a zero-day vulnerability tied to its MimbleWimble Extension Block (MWEB) privacy layer, prompting a 13-block chain reorganization that rewound about 32 minutes of activity.

“On April 25, the Litecoin network underwent a significant 13-block reorganization after attackers exploited a zero-day vulnerability in its MimbleWimble Extension Block (MWEB) privacy layer”

Bitbo

CoinDesk reported that the reorg rewound about 32 minutes and that “The Litecoin network ultimately reorganized back to the valid chain once denial-of-service attacks on patched miners ceased,” while also noting that the foundation “has not yet explained the patch timeline or disclosed how much LTC was affected during the invalid block window.”

Bitbo

Bloombergbit described the same core sequence: Litecoin said a zero-day bug triggered a DoS attack affecting some major mining pools, invalid MWEB transactions were confirmed by mining nodes that had not been updated, and Litecoin then “carried out a 13-block chain reorganization and voided all abnormal transactions that occurred during that period.”

CyberSecurityNews likewise tied the incident to invalid MWEB transactions accepted by unpatched nodes and said the response was a “13-block reorganization (reorg), a deliberate rollback mechanism that reversed the chain’s state to before the invalid transactions were included.”

The Block added that the Litecoin Foundation said the bug “enabled a denial-of-service attack against major mining pools” and that a 13-block reorganization reversed invalid transactions on the canonical chain, while also describing attackers using “the more than three-hour fork window” to attempt double-spends against cross-chain swap protocols.

Multiple outlets also described the same operational endpoint: the network returned to normal after the patch and reorg, with Bloombergbit stating “The vulnerability has been patched and the network is operating normally,” and CyberSecurityNews saying “The network is currently operating normally, with no ongoing disruption reported.”

In parallel, The Block reported that the Foundation said the bug is now fully patched, while also noting that “some trading venues have reported losses from the incident.”

A central dispute in the reporting concerns whether the exploited flaw was truly a zero-day or whether it had been privately patched before the attack.

CoinDesk said Litecoin’s foundation called the weekend exploit a zero-day, but then pointed to the litecoin-project GitHub repository showing the “consensus vulnerability was privately patched between March 19 and 26, more than four weeks before the attack.”

Bitcoin News

CoinDesk further described a “window in which some mining pools ran updated code while others remained vulnerable,” and said researchers “say the attackers appeared to have known which was which.”

The Block echoed the foundation’s public framing that the bug was a zero-day and that it was “fully patched,” but it also described the attack as targeting “mining nodes running older software” and said the Foundation “did not name the affected pools and did not disclose how much LTC the invalid MWEB transactions created.”

Cointelegraph reported that Alex Shevchenko, co-founder of Aurora, argued the bug was known rather than a zero-day, quoting him: “The fact that protocol automatically handled the reorg once DoS stopped, which is great, means that some portion of the hashrate was actually running an updated code. Thus, this bug was known, and it's not a zero-day.”

Cointelegraph also included a response from blockchain developer Vadim, writing: “The timing and targeting suggest this wasn't a random opportunity,” and “Low hashrate layer 1’s are not safe collateral for cross-chain value anymore.”

CoinDesk also stated that “The Litecoin Foundation has not publicly addressed the GitHub timeline as of Sunday morning,” and said the foundation “has not yet explained the patch timeline or disclosed how much LTC was affected during the invalid block window.”

Across outlets, the mechanics of the exploit were described as combining a denial-of-service component with a consensus flaw in MWEB that allowed invalid transactions to be accepted by nodes that had not updated.

CoinDesk said the attackers exploited a “patched, but not fully deployed, vulnerability in Litecoin’s MimbleWimble Extension Block protocol,” and that it triggered “a 13-block chain reorganization that rewound about 32 minutes of activity.”

CyberSecurityNews described the flaw as allowing threat actors “to inject an invalid MWEB (MimbleWimble Extension Block) transaction into unpatched nodes,” and it said the invalid transaction enabled “coins to be pegged out to third-party decentralized exchanges (DEXs) without proper authorization.”

MEXC similarly said “older nodes briefly enabling invalid transactions on the MWEB privacy layer,” and it described the attack as allowing “attackers reportedly manipulated cross-chain and DEX interactions during the event.”

The Block added that the bug allowed mining nodes running older software to validate “an invalid MWEB transaction,” letting whoever crafted it “peg coins out of the privacy extension and route them to third-party decentralized exchanges.”

CoinDesk also described a separate DoS vulnerability and said “A separate denial-of-service vulnerability was patched on the morning of April 25,” with both fixes “rolled into release 0.21.5.4 the same afternoon, after the attack had already begun.”

CoinDesk’s account of the chain response emphasized that “the network's longest valid chain corrected them,” and it said the invalid MWEB transactions “slip through nodes that had not updated, before the network's longest valid chain corrected them.”

The incident drew sharp reactions from crypto builders and researchers, particularly around whether the exploit was truly a zero-day and how patch adoption lag enabled the attack.

CoinDesk quoted Alex Shevchenko, CTO of NEAR Foundation's Aurora project, arguing that the denial-of-service and 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.”

bloomingbit

Cointelegraph carried Shevchenko’s direct argument that the reorg behavior undermined the zero-day framing, quoting: “The fact that protocol automatically handled the reorg once DoS stopped, which is great, means that some portion of the hashrate was actually running an updated code. Thus, this bug was known, and it's not a zero-day.”

Cointelegraph also quoted Vadim, writing on X: “The timing and targeting suggest this wasn't a random opportunity,” and it added his warning that “Low hashrate layer 1’s are not safe collateral for cross-chain value anymore.”

MEXC echoed these positions by describing Shevchenko’s thread and by stating that Vadim Zacodil argued that “the timing and targeting suggest this wasn't a random opportunity,” and that “low-hashrate layer-1s may no longer be reliable collateral for cross-chain value.”

CoinDesk also referenced a blockchain data point attributed to Shevchenko, saying “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.”

CoinDesk reported that the Litecoin Foundation “has not yet explained the patch timeline,” while also stating that “The Foundation said in Asian morning hours on Sunday the bug was fully patched and the network is operating normally.”

The immediate aftermath centered on the claim that the invalid MWEB transactions were erased from Litecoin’s canonical history, while other systems that interacted with those transactions during the fork window faced potential losses.

“Summary - Litecoin said a zero-day vulnerability triggered a denial-of-service (DoS) attack and affected some major mining pools”

bloomingbit

CyberSecurityNews stated that “all legitimate transactions processed during that period remain valid and unaffected,” and it said “Users and exchanges are not expected to experience any loss of funds related to the incident, according to the Litecoin development team’s post-incident statement.”

CoinDesk

CoinDesk, however, said the foundation “has not yet explained the patch timeline or disclosed how much LTC was affected during the invalid block window,” and it added that “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.”

The Block reported that “some trading venues have reported losses from the incident,” and it included Shevchenko’s estimate of exposure: “The exposure for NEAR Intents is around $600k.”

FinanceFeeds similarly said “Some platforms have reported losses, with one estimate placing exposure around $600,000,” and it described the broader risk as external systems remaining exposed even after the invalid transactions were removed.

Bitbo described market impact as minimal, saying “LTC traded around $56 with a 0.5% decline on the day,” while CoinDesk noted that the foundation had not disclosed the scope of affected funds.

In terms of operational response, CyberSecurityNews urged: “Update all Litecoin nodes to the latest patched release immediately,” and it also recommended “Monitor MWEB transaction activity for anomalous peg-out behavior” and “Establish automated alerting for chain reorganization events.”