Litecoin's 13-Block Reorg Wasn't a 'Zero-Day': GitHub Shows Fix Was Ready Five Weeks Earlier

Litecoin rolled back 13 blocks — about 32 minutes of chain history — after attackers exploited a MWEB consensus bug. The Litecoin Foundation called it a zero-day, but CoinDesk found the fix was privately developed between March 19 and 26.

Abstract red-amber glow signaling a chain-reorg incident on a major blockchain.
Litecoin rewinds 13 blocks after the MWEB exploit — the GitHub timeline complicates the "zero-day" framing.

Litecoin pulled off a 13-block chain reorganization on April 25, rewinding about 32 minutes of network activity after attackers exploited a vulnerability in its Mimblewimble Extension Block (MWEB) protocol. The Litecoin Foundation framed the bug as a "zero-day" — but the public GitHub history tells a different story.

What actually happened

The exploit chained two vulnerabilities. A denial-of-service bug took patched mining nodes offline; on the unpatched nodes that remained, attackers pushed through an invalid MWEB peg-out transaction. Both fixes were rolled into release 0.21.5.4 the same afternoon, and the network rolled the chain back to a clean state. Affected exchanges paused LTC deposits during the window; no end-user funds were lost.

The "zero-day" question

CoinDesk reporter Shaurya Malwa reviewed the litecoin-project repository and found that core developers had privately discovered and patched the MWEB consensus vulnerability between March 19 and March 26, 2026 — more than five weeks before the April 25 exploit. By the strict definition of a zero-day (no patch available at the moment of exploitation), the incident does not qualify. Critics on X argue Litecoin used the framing to soften the optics of a chain reorg on a top-25 asset.

Litecoin's 13-block reorg wasn't a zero-day, GitHub commit history shows otherwise
CoinDesk's Shaurya Malwa walks through the litecoin-project commit timeline and the holes in the Foundation's narrative.

What to Watch

Three threads worth tracking this week. First, exchanges that paused LTC deposits during the reorg — Binance, Coinbase, OKX — and how quickly they restore. Second, whether the Litecoin Foundation publicly addresses the GitHub timeline (silence so far). Third, the read-across to other privacy-extension proposals: MWEB-style opt-in privacy on Bitcoin (e.g., Silent Payments) inherits a similar surface area, and DeFi-native bridges that quoted Litecoin liquidity may pause integrations until they understand the reorg-risk window better.

Daily Web3 × AI intel, straight to your inbox. Subscribe to BlockAI News.

How we report: This article cites primary sources, regulatory filings, and on-chain data where available. BlockAI News uses AI tools to assist with research and first-draft generation; every article is reviewed and edited by a human editor before publication. Read our full How We Report page, Editorial Policy, AI Use Policy, and Corrections Policy.

Keep Reading

North Korea Hackers Crossed $6B in Crypto Theft — 76% of 2026 Losses From Two Bridge Attacks: TRM

North Korea Hackers Crossed $6B in Crypto Theft — 76% of 2026 Losses From Two Bridge Attacks: TRM

TRM Labs published its April 2026 hack accounting on April 30, and the headline number is the kind that resets industry assumptions: cumulative crypto theft attributable to North Korea-linked groups has crossed $6 billion since 2017, and Pyongyang now accounts for 76% of all 2026 hack losses through April — across just 3% of total incidents. Two April attacks did the work: a $292 million exploit of KelpDAO and a $285 million theft from Drift Protocol, totaling $577 million in a single month.

What actually

Read full story →

Stay Ahead of the Market

Daily AI & crypto briefings — straight to your inbox, your phone, and your timeline.