Cyber Incident Victim: Litecoin Cash
Date:
May 2018
Location:
United States of America
Summary
A cryptocurrency project experienced a 51% attack, compromising its blockchain integrity through majority hash power control. Developers confirmed the incident and responded by coordinating with exchanges to implement heightened security measures, including increasing mandatory network confirmations to at least 100. This event underscored systemic vulnerabilities in smaller proof-of-work cryptocurrencies susceptible to such attacks, reflecting a broader pattern of security challenges among emerging digital assets. The incident highlighted operational risks despite mitigation efforts following the breach.
| CIA Posture | Motives | Tactics, Techniques & Procedures |
|---|---|---|
| Available to members | 1 motive | 1 technique |
| Threat Actors | Type | Location |
|---|---|---|
| 0 actors | Available to members | Available to members |
Description
The Litecoin Cash (LCC) cryptocurrency experienced a 51% attack in late May 2018, as confirmed by its developers. This attack occurred when malicious actors gained majority control over the network's hash rate, enabling them to manipulate transactions and potentially execute double-spending. The incident was publicly acknowledged via social media, with a Twitter user (@ecurrencyhodler) noting the attack had taken place several days prior to their June 2018 post. Developers responded by coordinating with cryptocurrency exchanges to implement protective measures, specifically increasing the required number of network confirmations for transactions to at least 100 blocks. This adjustment aimed to reduce the risk of fraudulent transaction confirmations during the ongoing attack.
The attack underscored systemic vulnerabilities affecting smaller proof-of-work (PoW) cryptocurrencies, particularly those emerging as forks of established coins like Litecoin. Litecoin Cash, a separate entity from Litecoin despite its name, faced criticism for lacking adequate safeguards against such attacks at launch. The incident highlighted how spin-off projects could inherit security challenges without corresponding defenses. While no specific financial losses or technical disruptions were detailed in available reports, the developers characterized the event as a hard-learned lesson in blockchain security. The broader cryptocurrency community observed this as part of a concerning pattern of 51% attacks targeting low-hash-rate networks during that period.