Key Takeaways:
A Litecoin MWEB validation bug let an attacker inflate and peg out 85,034 LTC in March 2026, however the actor returned the funds for an 850 LTC bounty. An April 2026 exploit try triggered a 13-block chain reorg, inflicting NEAR Intents to lose 11,000 LTC swapped for 7.78 BTC. Litecoin Core v0.21.5.4 patches each the inflation bug and the mining node stall that enabled the April reorg.
Litecoin Builders Launch Postmortem After MWEB Bug Causes Chain Reorg
The postmortem recognized the foundation trigger as a lacking metadata test throughout block connection. When an MWEB enter spends a earlier output, the metadata it carries should match the precise UTXO being consumed. That test existed within the mempool and block-building paths, however builders confirmed it was not totally enforced on the block connection stage.
Builders found the vulnerability by means of inner overview on March 19. A series scan confirmed exploitation had already occurred at block 3,073,882. The attacker used a malicious MWEB enter whose actual worth was not more than 1.2084693 LTC to assist a pegout of 85,034.47285734 LTC.
Builders mentioned they coordinated privately with main mining swimming pools to include the inflated outputs earlier than public disclosure. An emergency launch, Litecoin Core 0.21.5, was pushed to miners to dam new malformed inputs. A follow-up launch, 0.21.5.1, added a historic exception for the already-accepted exploit block and quickly froze the three clear outpoints holding the attacker’s funds.
The actor tried to spend not less than one frozen output. Upgraded miners rejected the transaction. Builders then contacted the actor immediately. The actor agreed to cooperate and signed a restoration transaction that returned 84,184.47278630 LTC to a developer-controlled tackle whereas protecting 850 LTC as an agreed bounty.
Litecoin founder, Charlie Lee, bought the 850 LTC wanted to make the MWEB steadiness complete. The complete 85,034.47285734 LTC was pegged again into MWEB in a single transaction at block peak 3,078,098, and the ensuing MWEB output was frozen. No consumer funds have been finally misplaced within the March incident.
In keeping with the postmortem, a second attacker tried the identical exploit path in April, triggering a separate failure. Upgraded nodes rejected the malformed block, however the best way mutated MWEB block knowledge was dealt with precipitated sure mining RPC instructions to hold, together with the submitblock name. Upgraded mining nodes stalled whereas unupgraded miners continued extending the invalid chain.
The invalid chain grew to 13 blocks earlier than upgraded miners coordinated to overhaul it. The dangerous chain was reorged out, however a number of third-party techniques had already processed exercise on the invalid chain earlier than the reorg accomplished.
NEAR Intents confirmed the attacker swapped 11,000 LTC for 7.78814476 BTC earlier than the reorg accomplished. These 11,000 LTC have been now not current on the legitimate chain after the reorg, leaving NEAR Intents with a confirmed loss. Thorchain reported a separate loss after the attacker swapped 10 LTC for 0.00719957 BTC by means of its bridge earlier than the reorg.
Litecoin Core 0.21.5.4 addressed the mutated-block stall by erasing saved block knowledge for blocks labeled as mutated, permitting legitimate knowledge for a similar block hash to be accepted later. The discharge was constructed and deployed publicly on April 25.
The postmortem blogpost acknowledged a number of failures within the response, together with that MWEB validation relied too closely on checks that weren’t utilized at block connection, that the restoration required a number of staged miner releases every carrying coordination threat, and that the April mutated-block failure mode had not been examined towards mining RPC habits.
Neighborhood sentiment following the postmortem X put up was largely supportive, with roughly 70% to 80% of replies citing appreciation for the workforce’s transparency and pace. A number of responses famous that the chain itself held agency and that public disclosure constructed somewhat than broken belief.
Customers and node operators are suggested to improve to Litecoin Core v0.21.5.4 or later, confirm that their node is syncing usually, and reindex if the node stays caught after a restart. The postmortem follows Litecoin’s latest put up about doing higher with regards to posting on X. “These in control of posting from this [X] deal with will do higher sooner or later,” the official Litecoin X account wrote after the account was accused of being “infantile” earlier within the week.
