bigone-hacked-users-lose-27-million-in-hot-wallet-exploit
BigONE faces a $27 million hot wallet hack, impacts include Bitcoin, Ethereum, USD Tether losses.
Key Points:

  • Main event, leadership changes, market impact, financial shifts, or expert insights.
  • BigONE confirms reimbursement for user losses through reserves.
  • Security measures enhanced to prevent future breaches.

BigONE, a crypto exchange, experienced a significant hack on its hot wallet infrastructure, resulting in losses of $27 million, confirmed on July 16, 2025.

BigONE’s hack underscores ongoing security risks in the cryptocurrency sector, prompting immediate efforts to fortify digital infrastructure and assure market stability.

BigONE’s hot wallet was compromised, leading to a loss of $27 million in digital assets. The exchange is engaged in collaboration with SlowMist for investigations.


Official BigONE Statement, BigONE, “Upon investigation, it was confirmed to be the result of a third-party attack targeting our hot wallet. All private keys remain secure, and the attack path has been identified and contained to prevent further losses.” – source

The breach involved assets like Bitcoin, Ethereum, and USD Tether. BigONE aims to fully compensate users via internal reserves, external borrowing, and enhanced security measures.

Major assets affected include 120 BTC, 350 ETH, and over $8.5 million in USDT. Deposits and trading were temporarily halted but are now largely restored.

The hack highlights security concerns for centralized exchanges, paralleling recent vulnerabilities seen in the industry. The exchange assures swift compensation for affected users.

Regulatory responses remain absent following this incident, though the use of blockchain tracking might prompt future oversight improvements.

BigONE’s response exemplifies industry trends toward compensatory measures and heightened technological vigilance, emphasizing the need for comprehensive security protocols to safeguard user assets.

Leave a Reply

Your email address will not be published. Required fields are marked *