TL;DR
- October 20, 2016: Ethereum experiencing ongoing “Shanghai attacks” – persistent DDoS exploiting mispriced opcodes
- BTC price: $630.86 | ETH price: $12.10 | Market cap: $11.08B
- EIP 150 hard fork released on October 18, 2016 to fix critical security vulnerabilities
- Attackers created ~19 million empty accounts overwhelming blockchain infrastructure
- Network security becoming critical concern as adoption expands
Network Under Attack
As the Ethereum blockchain entered late October 2016, the network found itself under sustained attack from malicious actors exploiting critical vulnerabilities in the protocol design. What began earlier in the month as testing of network limits had evolved into a coordinated campaign known as the “Shanghai attacks,” named for the location of the second Ethereum Developers’ Conference where the attacks were first observed. These attacks represented one of the most serious security challenges faced by the Ethereum network since its launch, forcing developers to implement emergency hard fork measures to protect the blockchain.
The Shanghai Attack Begins
The attacks originated during the second Ethereum Developers’ Conference in Shanghai in October 2016. Blackhat hackers began probing the Ethereum blockchain, systematically exploiting weaknesses in the network’s design. The attackers focused on mispriced opcodes within the Ethereum Virtual Machine (EVM) – specific operations that consumed relatively little computational gas compared to their actual processing requirements. This pricing imbalance allowed malicious actors to overwhelm Ethereum nodes with computationally expensive tasks while paying minimal transaction fees.
The primary attack vector involved creating empty accounts on the blockchain in a cost-effective manner. While the Ethereum protocol already had mechanisms to account creation fees, the attackers discovered a way to circumvent these safeguards by leveraging the selfdestruct opcode. This allowed them to flood the network with empty accounts, dramatically increasing the blockchain’s size and storage requirements while providing no legitimate economic value.
EIP-150 Emergency Response
In response to the escalating attacks, the Ethereum development team implemented the EIP 150 hard fork on October 18, 2016 – just two days before our current date. This emergency measure was designed to address the fundamental vulnerabilities being exploited by the attackers. EIP 150 (also known as the “Gas Price Changes” fork) implemented several critical fixes:
The hard fork dramatically revised gas costs for several opcodes that were significantly underpriced, making them economically unfeasible for attack purposes. It also introduced changes to how the network handled state operations, particularly around account creation and destruction. The timing was critical – the fork had to be deployed quickly enough to prevent further exploitation of the vulnerabilities, but carefully enough to ensure proper testing and community consensus.
Mispriced Opcodes and the Exploit
The technical details of the Shanghai attacks revealed fundamental challenges in blockchain security design. The attackers had identified specific opcodes within the EVM where the computational cost far exceeded the gas price. For example, certain operations that required significant processing time only consumed minimal gas units, creating an economic incentive for abuse.
One particularly concerning aspect was the creation of empty accounts. The protocol had long distinguished between zero-balance and nonexistent accounts, but the attackers found ways to create intermediate account states that were technically empty but still consumed storage space. These empty accounts were created using the selfdestruct opcode in ways that bypassed existing fee structures.
The sheer scale of the attack was staggering – attackers created approximately 19 million empty accounts across the blockchain. This represented a massive burden on network storage requirements and processing capacity, potentially jeopardizing the long-term viability of the Ethereum network if left unaddressed.
Community Response and Development
The Shanghai attacks underscored both the strengths and vulnerabilities of open-source blockchain development. The Ethereum community responded rapidly to the crisis, with developers working around the clock to implement and deploy the EIP 150 hard fork. This collaborative approach highlighted the network’s resilience in the face of security challenges.
Developers from across the ecosystem contributed to the response, analyzing attack patterns, implementing fixes, and communicating with the community about both the risks and mitigation strategies. The open nature of Ethereum’s development process allowed for rapid identification and resolution of security issues, though it also meant that vulnerabilities were visible to potential attackers.
Broader Implications for Blockchain Security
The attacks that targeted Ethereum in October 2016 served as an important case study for the broader cryptocurrency ecosystem. They demonstrated that even relatively sophisticated blockchain protocols could have critical security vulnerabilities that, once discovered, could be exploited with devastating consequences.
The incident highlighted the importance of rigorous security audits and ongoing protocol maintenance. It also showed that blockchain networks needed to be designed with the assumption that vulnerabilities would be discovered and exploited, rather than relying on security through obscurity.
For developers and users alike, the Shanghai attacks served as a reminder that blockchain security was not a one-time concern but an ongoing process requiring constant vigilance, regular updates, and community cooperation.
Why This Matters
The “Shanghai attacks” on the Ethereum network in October 2016 represent a pivotal moment in blockchain security history. At a time when cryptocurrencies were beginning to gain mainstream attention, the attacks demonstrated that even relatively mature blockchain networks faced significant security challenges that could threaten their fundamental viability.
For the Ethereum community, the incident proved the network’s resilience through rapid, collaborative response. The successful implementation of EIP 150 demonstrated that the protocol could adapt to critical security threats while maintaining network consensus and continuity.
For the broader cryptocurrency ecosystem, the Shanghai attacks served as an important lesson about the importance of ongoing security research and protocol maintenance. As blockchain adoption expanded beyond early adopters and into mainstream consciousness, the need for robust security frameworks became increasingly apparent.
The attacks also highlighted the delicate balance between blockchain openness and security. While open development and transparency are core strengths of blockchain technology, they also make protocols vulnerable to discovery of vulnerabilities that could be exploited by malicious actors. This balance would continue to be a critical consideration for blockchain developers in the years to come.
As we look back on October 20, 2016, the ongoing Shanghai attacks and the Ethereum community’s response represent a crucial step in the maturation of blockchain security practices. The incident demonstrated that blockchain networks were not infallible, but they also showed that the community’s ability to respond to security challenges was a key strength of the technology.
Disclaimer: This article is for informational purposes only and should not be considered financial advice. Cryptocurrency investments carry significant risk and should be made only after thorough research and consideration of individual circumstances.
EXTCODECOPY costing nothing in gas was a nuke waiting to go off. 19M spam accounts for a few grand is asymmetric warfare
warship_vel_ and the fix shipped in 48 hours. modern L1 governance takes 6 months to change a fee parameter
Kari N. wartime shipping velocity. ETH at 12 bucks and the core devs just got it done. no 47-page governance proposal needed
Good breakdown of the attack mechanics. The part about mispriced EXTCODECOPY opcodes is key — that was the specific vector the attacker kept exploiting before EIP-150 adjusted the costs.
Interesting that this analysis version covers the same events but the expert angle on gas repricing consequences is what most people missed at the time. Contract costs went up significantly.
EXTCODECOPY repricing was elegant. instead of patching the attack they just made it economically unviable. gas costs as a security mechanism
Piotr G. EIP-150 was a masterclass in economic defense. instead of patching each attack vector individually they repriced the entire opcode gas schedule. one fork solved dozens of attack vectors at once
Oleh K. EIP-150 repriced the entire opcode schedule in one fork instead of playing whack-a-mole with individual attack vectors. one of the best governance decisions in eth history
the EXTCODECOPY repricing in EIP-150 was the real fix. before that attackers could spam it for basically zero gas and clog the entire chain for hours
opcod3r EXTCODECOPY repricing was the cleanest fix possible. no hard fork drama, no consensus change, just made the attack economically unviable. elegant
reorg_drifter_ exactly. the asymmetry was insane. a few grand in gas to bring the chain to its knees. EIP-150 repricing was surgical
greta the asymmetry was the real lesson. a few grand in gas to nearly kill a billion dollar network. EIP-150 fixed the pricing but the lesson about economic attack vectors stuck forever
ETH at $12.10 during the attacks. anyone who bought and held is up something like 250x. max pain builds conviction
cuda_dreams ETH at $12 during the attacks and now its how much. anyone who bought during maximum chaos and held is sitting on generational wealth
19 million empty accounts created just to bloat the state. the attacker spent maybe a few thousand dollars in gas to do millions in damage to the network
a few thousand in gas to do millions in damage. the asymmetry of attack vs defense on early ETH was brutal
eth_vintage a few thousand in gas to do millions in damage. the attack asymmetry on early eth was insane. EIP-150 repricing was the only real fix and it worked instantly
19 million empty accounts from a few thousand dollars in gas. the attacker weaponized ETHs own account creation mechanics against it. brilliant and terrifying
spambot_slain 19 million empty accounts from a few grand in gas. the attacker understood ETH economics better than most developers did at the time
spambot_slain weaponizing account creation was genius in a evil way. 19 million empty accounts costing nothing to create but clogging the chain for everyone else
ETH at 12 dollars during the attacks and the network still survived. says a lot about the core dev teams ability to ship emergency fixes under pressure
Konrad J. 48 hours from incident to hard fork. modern L1 governance takes 6 months to change a fee parameter
opcode_panic_ 48 hours is wild. but EIP-150 was controversial too. vitalik had to push back on miners who hated the gas limit changes. the speed came with political cost
EXTCODECOPY costing basically nothing in gas was such an obvious vector. hard to blame pre-EIP-150 devs though, nobody thought someone would spam 19 million empty accounts for the lulz
ETH at 12 bucks during the Shanghai attacks. imagine the stress on the core devs knowing the entire network could grind to a halt if EIP-150 didnt work
Eliska N. they shipped EIP-150 in 2 days. compare that to how long governance takes on modern L1s. early ETH had actual wartime shipping velocity
ETH at 12 dollars during the attacks and the dev team shipped a hard fork in 48 hours. try getting any modern L1 governance to move that fast lol