Litecoin developers have published a postmortem confirming that two security incidents in March and April 2026 were tied to a critical validation flaw in Mimblewimble Extension Block, or MWEB. The bug first allowed an attacker to fabricate a pegout of 85,034.47285734 LTC, and a later exploit attempt contributed to a 13-block chain reorganization that affected third-party systems including Thorchain and NEAR Intents.
Root cause traced to missing validation at block connection
According to the report, the issue came from a missing metadata check during block connection. In MWEB, when an input spends a previous output, its metadata must match the actual UTXO being consumed. Developers said that check existed in mempool and block-building logic, but was not fully enforced when blocks were connected to the chain, creating an opening for exploitation.
The vulnerability was identified during an internal review on March 19. A scan of the chain showed that it had already been exploited at block height 3,073,882. The attacker used a malicious MWEB input with a real value of no more than 1.2084693 LTC to support a pegout worth 85,034.47285734 LTC.
Emergency containment, fund freeze, and negotiated recovery
After confirming the exploit, the team privately coordinated with major mining pools to contain the inflated outputs before disclosing the issue publicly. An emergency release, Litecoin Core 0.21.5, was pushed to miners to block new malformed inputs. A follow-up release, 0.21.5.1, added a historical exception for the already accepted exploit block and temporarily froze three transparent outpoints holding the attacker’s funds.
The postmortem says the attacker later tried to spend at least one frozen output, but upgraded miners rejected the transaction. Developers then contacted the actor directly, and the two sides reached an agreement. The attacker signed a recovery transaction returning 84,184.47278630 LTC to a developer-controlled address while keeping 850 LTC as a bounty. Litecoin founder Charlie Lee purchased the additional 850 LTC needed to restore the MWEB balance. The full 85,034.47285734 LTC was then pegged back into MWEB in a single transaction, and the resulting output was frozen. Developers said no user funds were ultimately lost in the March incident.
April exploit attempt triggered reorg and third-party losses
A second attacker attempted to use the same path in April, but the outcome was different. While upgraded nodes rejected the malformed block, the way mutated MWEB block data was handled caused certain mining RPC calls, including submitblock, to hang. That left upgraded mining nodes stalled while unupgraded miners continued building on an invalid chain.
The invalid chain eventually grew to 13 blocks before upgraded miners coordinated to overtake it. By the time the bad chain was reorged out, several third-party platforms had already processed transactions on it. NEAR Intents said the attacker swapped 11,000 LTC for 7.78814476 BTC before the reorg completed, creating a confirmed loss because those LTC did not exist on the valid chain afterward. Thorchain also reported a separate loss after the attacker swapped 10 LTC for 0.00719957 BTC through its bridge.
Patch released as Litecoin urges upgrades
To address the second failure mode, Litecoin Core 0.21.5.4 was released with logic to erase stored data for blocks classified as mutated, allowing valid data for the same block hash to be accepted later. The build was publicly deployed on April 25.
The team acknowledged several shortcomings in its response, including overreliance on validation checks that were not enforced during block connection, the coordination risk created by staged miner releases, and the fact that the April mutated-block scenario had not been tested against mining RPC behavior. Litecoin is advising users and node operators to upgrade to v0.21.5.4 or later, confirm their nodes are syncing normally, and reindex if a node remains stuck after restart.