Qubic Restarts Blockchain After $1.4 Million Wallet Security Breach
Key Takeaways
- •The security incident affected wallet seeds generated by vulnerable Qubic web wallet software on certain Apple devices and browsers.
- •Qubic halted the network, secured affected funds in escrow, and resumed operations after validators approved the recovery plan.
- •Affected users can check eligibility and submit claims through Qubic’s reclaim platform until May 1, 2027.
- •Qubic recommends that users of earlier wallet versions create new wallets and move remaining funds after upgrading to version 4.26.4 or later.

Qubic has brought its blockchain back online after temporarily halting the network to contain a security flaw that allowed attackers to steal approximately $1.4 million worth of QU tokens from 1,404 accounts. The layer-1 project has also opened a recovery process for affected users, with claims accepted through May 1, 2027.
Coordinated pauses followed by validator-approved restarts are uncommon among layer-1 networks, where on-chain finality typically leaves theft victims with little recourse. That is what makes the scope of this response — a full halt, funds secured in escrow, and a formal claims process — worth noting.
Processing resumed at 8:00 p.m. on October 19, with the chain advancing past tick 85,371,949, the point at which operations had been frozen following the security incident. According to the project, the suspension was a containment measure intended to limit further movement of stolen funds while the team addressed the vulnerability and developed a recovery plan. The tick number gives observers a verifiable reference point for exactly where the chain stopped and picked back up.
The network's validators, known as Computors, approved the recovery plan and launched a dedicated reclaim platform through which affected wallet holders can check their eligibility and submit claims. The extended deadline gives impacted users several months to verify their accounts and complete the required procedures. Because the halt allowed affected funds to be moved into a protected escrow rather than left exposed, a structured claims process became feasible.
How Predictable Seeds Led to the Theft
At the center of the incident were predictable wallet seeds generated by vulnerable versions of Qubic's web wallet software. Seeds are foundational to wallet security because they help produce the cryptographic keys that control and authorize transactions involving digital assets.
Per the project, the flaw affected seeds created through its web wallet on certain Apple devices and browsers. An insecure random-number generator could produce predictable seeds, potentially letting attackers derive wallet credentials and access funds without authorization. The downstream impact follows directly: every key a wallet derives inherits the quality of the randomness it started from, so weak entropy at creation undermines everything built on top of it.
The weakness raised concerns about wallets created with the affected software, since unpredictable seed generation is fundamental to protecting cryptocurrency holdings. If an attacker can reproduce a wallet's seed, the funds it controls may be at risk even if the legitimate holder has never disclosed any credentials.
Qubic paused its chain to cap the potential fallout and prevent further movement of compromised assets while remediation work was underway. Network operations were restored once the validators approved the recovery arrangements.
While the network was halted, the affected funds were moved into a protected escrow instead of staying exposed. That made recovery possible. The quorum approved it, and the network has resumed normal operation.
— Qubic (@Qubic) October 20, 2026
Users Urged to Create New Wallets
Qubic said it addressed the vulnerability in web wallet version 4.26.4, released on October 19. The update alone, however, does not eliminate the risk tied to wallets created with earlier versions of the software.
The project has urged users who created wallets with previous web wallet versions to treat those wallets as insecure, upgrade to version 4.26.4 or later, new wallets, and transfer any remaining funds as soon as possible.
The caution is warranted because updating wallet software may not change the underlying seed or cryptographic credentials of an existing wallet. Creating a new wallet and moving assets into it helps users avoid continued reliance on credentials that the vulnerability may have exposed.
Users are also advised to confirm they are using the project's genuine wallet and recovery services before entering sensitive information or moving funds. Because cryptocurrency transactions are generally difficult to reverse, careful verification is essential during any security incident — particularly now, since fake recovery portals and impersonation accounts routinely trail high-profile crypto breaches.
Recovery Process and Security Implications
The reclaim platform gives affected holders a formal route to check whether their wallet addresses were impacted and to file claims under the approved recovery plan. The project has directed users to follow its official instructions and finish the process ahead of the May 1, 2027 deadline. From here, the practical items to watch are the claims deadline itself and any further published detail on how claims will be evaluated and paid out.
The episode illustrates how weaknesses in wallet generation can cause damage even when the underlying blockchain itself remains operational. Predictable cryptographic seeds can undermine wallet security and expose digital assets to unauthorized access.
For Qubic, bringing the network back online addresses only part of the problem. The recovery process, wallet migration guidance, and the fix for the random-number generator flaw are equally central to limiting further losses and rebuilding user confidence.
The project has not indicated in the announcement whether all stolen funds can be recovered. Affected users should therefore distinguish between submitting a claim and actually receiving reimbursement, as the outcome will depend on the terms and implementation of the recovery plan.
The incident ultimately underscores the importance of secure random-number generation, timely software updates, and proactive wallet migration whenever vulnerabilities threaten private-key security across blockchain ecosystems.