
Ice Open Network wrote on X on April 20, confirming the data breach that occurred last week. The cause was that after four partners ended their business relationship with a third-party service provider, they still accessed external servers, leaking users’ email addresses, 2FA phone numbers, and identity-linked data. The background of this incident is that the ION token had already crashed by 93% two weeks ago, and the project team is in a period of large-scale emergency restructuring.
Ice Open Network clearly stated that this incident was not caused by a hack of the core protocol, but by misuse by insiders in outsourced operations—specifically, a security failure in the third-party service supply chain, not a technical vulnerability in the core system. After leaving their jobs, the four partners continued to access external servers, leaking users’ email addresses, phone numbers (used for 2FA verification), and identity-linked data, raising serious privacy concerns. Affected users were advised to immediately update their two-factor authentication (2FA) settings to prevent unauthorized access to their accounts.
This data breach came on top of the token crash crisis from two weeks earlier. On April 7, the ION token fell from $0.003 to $0.00024, a drop of as much as 93%. The CEO blamed the crash on a longtime service provider offloading tokens (described as a “capital shock”), but did not provide verifiable on-chain evidence. At the time, the company also disclosed that it had already spent $18 million, burn rate was $400k per month, and it was nearing a financial crisis.
However, within 48 hours, the situation took a dramatic turn: monthly costs were cut by 89% to about $45k, staff were reduced to core developers, and an 8-week roadmap was introduced with a final goal of a “$1 billion valuation.”
In response to this data breach, Ice Open Network has taken action: a formal complaint has been filed with the ICO, and legal proceedings are in progress; it plans to carry out a technical migration on April 21 to strengthen security, but the Online+ platform is expected to experience temporary service interruptions during this period. This incident has also drawn broader industry attention in the background—during the first half of April 2026, losses from global crypto security incidents had already exceeded $606 million, indicating that security threats are rapidly heating up.
No impact. The company stated clearly that neither private keys nor wallets were affected, the core blockchain was not attacked, and there were no direct financial losses. What was leaked were identity-related metadata (email addresses and 2FA phone numbers), not funding access credentials.
The CEO said the crash was due to a longtime service provider offloading large amounts of tokens, but did not provide verifiable on-chain evidence. When this crash occurred, the company simultaneously disclosed that it had already spent $18 million and was nearing a financial crisis; these timing points have led the community to broadly question internal financial management.
This target is currently facing severe challenges: the token has already crashed by 93%, the company has just urgently cut monthly spending from $400k to $45k, and at the same time is facing a trust crisis caused by the data breach. The feasibility of the 8-week roadmap still needs to be verified by subsequent execution.
Related Articles
PreSPAX Pre-Trading Rises 8.83% to $652.99, Hits 24-Hour High of $662
Altcoins Surge Back Above $1.3T as Markets Rally After Greenland Crisis Resolution
ARB Recovery Gains Steam as Staking Yields Jump Above 221%