Crypto News
A zero-day vulnerability in Litecoin's codebase was exploited on April 25, triggering a 13-block reorganization that temporarily halted transaction finality across major mining pools. Un-updated nodes incorrectly accepted an invalid MWEB (MimbleWimble Extension Block) transaction, which a denial-of-service attack exploited to flood the network and peg out coins to third-party DEXs. The Litecoin team confirmed the bug on their official X account and said a patch has been fully deployed, urging node operators to update immediately.
Why it matters
A 13-block reorg is not a rounding error. For a proof-of-work chain the size of Litecoin, a reorg of that depth qualifies as a serious network event by any measure — the kind of incident that triggers exchange deposit pauses, custody provider reviews, and miner reassessments of software exposure. The bug appears to have hit nodes that had not updated to the latest MWEB release, meaning the network's resilience during the attack depended on the share of mining power running current code.
Market impact
No user funds were reported lost, and the invalid transactions reversed by the reorg will not be honored — the network's consensus rules did the job they were designed to do. LTC price action has been messy but not collapsing, holding a sideways range while broader crypto markets navigate fragile sentiment around Bitcoin near key resistance. The structural levels to watch are $60 on the upside, where a clean break could reopen the top of the range, and $52 on the downside, where a failure would open a faster move lower.
Frequently asked questions
-
What happened to Litecoin on April 25?
A zero-day vulnerability in Litecoin's codebase was exploited on April 25, triggering a 13-block reorganization that temporarily halted transaction finality across major mining pools. The Litecoin team confirmed the bug and said a patch has been fully deployed.
-
Was the Litecoin hack a 51% attack?
No — the root cause was un-updated nodes accepting an invalid MWEB (MimbleWimble Extension Block) transaction, which a denial-of-service attack then exploited to flood the network. The 13-block reorg was the network's consensus rules reversing the invalid transactions.
-
Did any user funds get lost in the Litecoin hack?
No user funds were reported lost. The 13-block reorg reversed the invalid transactions, and the network's consensus rules invalidated them rather than allowing the attempted peg-out to third-party DEXs to stand.
-
What is a 13-block reorg and why does it matter?
A reorg of that depth on a proof-of-work chain the size of Litecoin qualifies as a serious network event, not a routine orphan-block cleanup. It typically triggers exchange deposit pauses, custody provider reviews, and miner reassessments of software exposure.
-
What should Litecoin node operators and miners do now?
The Litecoin team urged node operators to update to the latest patched release immediately. Mining pools running un-updated MEB code were the ones that accepted the invalid transaction, so staying current on node software is the primary mitigation.
TheBlock
CoinTelegraph
WuBlockchain
CoinDesk
Lookonchain