Cryptocurrency Security Report: June Records $111.6 Million in Hack Losses

·

According to cybersecurity analysts, the cryptocurrency industry suffered approximately $111.6 million in losses due to major security breaches in June 2025. This represents a notable 56% decrease compared to the previous month’s figures. Around 15 significant hacking incidents were documented, highlighting ongoing vulnerabilities in the digital asset space.

The most severe attack targeted the Iranian exchange Nobitex, resulting in losses estimated at $82 million. Reports suggest the breach was linked to hackers associated with Israel. Other major exploits included ResupplyFi, which lost $9.6 million, ALEXLabBTC with $8.4 million in damages, and ForceBridge, which suffered a $3.8 million loss. Additionally, an individual user on the Solana network was compromised, leading to a theft of $3.2 million.

Overview of Major Incidents

Nobitex Exchange Attack

The attack on Nobitex dominated the month’s security incidents, both in scale and sophistication. The $82 million loss underscores the persistent risks associated with centralized exchanges, particularly those operating in high-risk jurisdictions.

DeFi and Cross-Chain Vulnerabilities

Protocols like ResupplyFi and ForceBridge illustrate the technical challenges still facing the decentralized finance (DeFi) sector. Cross-chain bridges, in particular, remain a prime target for attackers due to the complexity of their smart contracts and the value they lock.

Individual User Security

The Solana user incident, involving $3.2 million, is a reminder that individual wallets are not immune to threats. Phishing, private key compromise, and signing malicious transactions are common methods used to target retail participants.

Understanding the Decline in Hacks

The significant month-over-month reduction in losses is a positive signal for the industry. This decline may be attributed to several factors:

Despite this progress, the absolute value of losses remains alarmingly high, indicating that security must remain a top priority for all participants in the ecosystem.

How to Protect Your Crypto Assets

Whether you are a protocol developer or an individual investor, prioritizing security is non-negotiable. Here are some foundational best practices:

Staying informed about the latest threats and defensive strategies is crucial for navigating the space safely. You can 👉 explore more security strategies to deepen your understanding.

Frequently Asked Questions

What was the total value lost to crypto hacks in June 2025?
The total estimated losses from cryptocurrency hacks and exploits in June 2025 reached $111.6 million. This figure represents a significant decrease from the amount lost in May.

Which incident was the largest attack in June?
The largest single incident was an attack on the Iranian exchange Nobitex, which lost approximately $82 million. The breach was reportedly carried out by hackers with links to Israel.

Are DeFi protocols still a major target for hackers?
Yes, decentralized finance protocols and cross-chain bridges continue to be attractive targets due to the complexity of their code and the large sums of liquidity they often hold. Incidents involving ResupplyFi and ForceBridge are examples from June.

How can I keep my personal cryptocurrency holdings secure?
The best practices include using a hardware wallet for cold storage, never sharing your seed phrase, enabling 2FA on all exchange accounts, and double-checking all website URLs and smart contract permissions before interacting with them.

Why is there a monthly variance in crypto hack losses?
The totals fluctuate based on the number of successful attacks and the scale of the protocols targeted. A single large exploit, like the one on Nobitex, can dramatically inflate a month's total losses. Enhanced security measures across the industry can also lead to decreases.

What should I do if I discover a vulnerability in a protocol?
If you identify a potential smart contract vulnerability or security flaw, you should responsibly disclose it to the project team through their official bug bounty program (if one exists) or a dedicated security channel. Avoid making the exploit public before the team has a chance to patch it.