Ethereum and Solana Dominate 2026 H1 Crypto Hack Losses, Surpassing $1 Billion

1 billion dollars in hack losses, with Ethereum and Solana emerging as the top victim chains in H1 2026, reignites security concerns across the crypto ecosystem.

H1 2026’s Record Hack Surge

Blockaid’s latest security report documents 212 incidents and a staggering $1.0 billion in stolen funds—exceeding the total loss of the entire 2025 year.

Ethereum: The Dark Side of Code

■$332 million loss, with a single blow from KelpDAO costing $292 million.

■Code bugs and bridge vulnerabilities accounted for $200 million+ in losses.

■Humanity Protocol and StablR key compromises added $50 million.

■A lone user error at CoWSwap resulted in $5 million.

Solana: The Key‑Loss Catastrophe

■$326 million total loss, largely due to key breaches in Drift Protocol and Step Finance (98 % of Solana’s total).

■Remaining $5 million from code exploits in Raydium and Volo.

■North‑Korea linked cyber groups amplified losses from $127 million in 2025 to a sharp increase.

The 212 Incident Landscape

■High‑threshold attacks rose 3.4× compared to 2025.

■The largest single exploit was KelpDAO’s $292 million theft.

■Ethereum had 70 % code‑based exploits; Solana had 98 % key‑based breaches.

2025 vs 2026: Escalating Threats

■2025’s total loss was $2.58 billion, driven by Bybit’s $1.5 billion single incident.

■In 2026, Ethereum and Solana each exceeded $330 million losses—more than double the single‑incident peak of 2025.

Key Numbers and Highlights

■Ethereum: $332 million – Code errors, bridge exploits, key breaches.

■Solana: $326 million – Key breaches, organizational security gaps.

■KelpDAO: $292 million – Largest single incident.

■Bybit (2025): $1.5 billion – Largest single incident of 2025.

The surge in crypto security breaches underscores that the issue is not purely technical; organizational risk management is equally critical. Ethereum’s code‑based attacks versus Solana’s key‑based intrusions highlight two distinct vulnerabilities. Investors and developers must adopt proactive countermeasures against both to mitigate future losses.