ASTEROID Whales Pivot to New Memecoins but Lose All of Their Money
A top ASTEROID whale lost all their money after pivoting to a new memecoin. What went wrong?
U.Today1 min read
Here’s How Litecoin (LTC) Contained a Massive MWEB Exploit
TL;DR
Litecoin faced a major disruption due to a validation flaw in its MWEB privacy layer, exploited in March and April 2026. An attacker inflated a pegout of over 85,000 LTC, but most funds were later recovered after negotiations.
Key points
- Litecoin's MWEB privacy layer had a critical validation flaw
- An attacker exploited the flaw to inflate pegouts over 85,000 LTC
- Most funds were recovered after negotiations with the attacker
Mentioned in this story
David Burkett
MimbleWimble Extension Block
Litecoin experienced a significant disruption tied to its MimbleWimble Extension Block (MWEB) privacy layer after a critical validation flaw was discovered and exploited across two separate incidents in March and April 2026, according to a post-mortem shared by developer David Burkett.
The issue originated from a bug in how MWEB inputs were validated during block connection, which allowed a miner to include malformed metadata that did not match the actual unspent transaction output being referenced. This enabled an attacker to construct a block where a relatively small input appeared to justify a much larger withdrawal, known as a pegout, from the MWEB system.
Timeline of MWEB Crisis
Interestingly, a chain scan revealed that the vulnerability had already been exploited in March at block height 3,073,882, where an attacker generated an inflated pegout of over 85,000 LTC. The funds were initially moved to a transparent address and split across three outputs, which were quickly temporarily frozen by miner-enforced consensus rules.
Developers privately worked with major mining pools to prevent further exploitation and released a series of emergency updates to enforce stricter validation rules while preserving network stability. The attacker later cooperated after being contacted and signed a recovery transaction that returned the majority of the funds, while retaining 850 LTC as a negotiated bounty.
That shortfall was covered separately by Litecoin creator Charlie Lee, and the full recovered amount was pegged back into MWEB. The resulting output was permanently frozen to restore internal balance. No confirmed user funds were lost in the March incident, though the response relied heavily on rapid miner coordination and controlled software rollouts.
A second incident in April exposed additional complications when another actor attempted to reuse the same exploit path. Although updated nodes correctly rejected the malformed block, the handling of mutated MWEB block data caused certain upgraded mining nodes to stall or become unable to continue normal operations. This particularly affected block submission processes.
As a result, unupgraded miners continued extending an invalid chain, which grew to 13 blocks before upgraded participants coordinated to restore the valid chain, which ended up triggering a deep reorganization. This reorg removed the invalid blocks, but not before some third-party systems processed transactions from the bad chain.
External services were impacted, including swaps conducted through NEAR-related infrastructure and THORChain, where assets exchanged on the invalid chain no longer existed after the reorg. Losses tied to these transactions are still being assessed.
Q&A
What was the MWEB exploit in Litecoin?
The MWEB exploit involved a validation flaw that allowed an attacker to create a block with inflated pegouts, leading to the unauthorized withdrawal of over 85,000 LTC.
How did Litecoin recover from the MWEB exploit?
Litecoin developers collaborated with major mining pools to implement emergency updates and negotiated with the attacker, resulting in the recovery of most funds.
What are the implications of the MWEB validation flaw for Litecoin users?
The validation flaw raised concerns about the security of the MWEB privacy layer, prompting developers to enhance validation rules to protect users and maintain network stability.
