# Qubic Restarts Blockchain Following $1.4M Wallet Seed Vulnerability Hack

Network validators approve recovery plan as users submit claims for stolen tokens.

- **Source:** [Cointelegraph.com News](https://brifing.si/source/2e81e982-0137-4db0-8ac2-351f37085775)
- **Published:** 2026-10-20
- **Topic:** [Software & Engineering](https://brifing.si/c/engineering)
- **Original article:** <https://cointelegraph.com/news/qubic-restarts-blockchain-opens-recovery-claims-after-14m-hack?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound>
- **On Brifing:** https://brifing.si/s/101abeff-4d33-43ad-9d32-e0e03a948509

## Network Resumption After Halt

Qubic officially restarted its layer-1 blockchain operations on October 19, 2026, following a temporary suspension. The network successfully resumed processing ticks beyond tick 85,371,949. This pause was a strategic measure implemented by validators to prevent further unauthorized movement of funds after an attacker exploited a critical vulnerability within the system.

## Scope of Financial Impact

The security breach resulted in the loss of approximately $1.4 million worth of QU tokens. Data indicates that 1,404 individual accounts were compromised during the incident. The project team confirmed these figures in their latest update, highlighting the scale of the exploit that necessitated the immediate network-wide halt to protect remaining assets.

## Root Cause Analysis

The exploit originated from a vulnerability in the wallet seed generation process. Specifically, the web wallet software used on certain Apple devices and browsers utilized an insecure random-number generator. This flaw produced predictable seeds, allowing attackers to gain unauthorized access to user accounts. The team has since addressed this specific software defect.

## Recovery Plan Implementation

Qubic’s network validators, known as Computors, have formally approved a comprehensive recovery plan to address the losses. A dedicated claims platform is now live, allowing affected wallet holders to verify their addresses and submit formal recovery requests. This mechanism serves as the primary channel for users to seek restitution for their stolen funds.

## Submission Deadlines and Process

Affected users have a clear timeline to participate in the recovery process. The project has set a final deadline of May 1, 2027, for all claim submissions. Users must utilize the official Qubic reclaim platform to initiate their requests, ensuring that all necessary address verification steps are completed before the specified cutoff date.

## Mandatory Security Upgrades

The development team released version 4.26.4 on October 19 to patch the seed-generation flaw. Any wallet created via the web interface prior to this version is now considered insecure. Users are strictly advised to migrate all funds to a newly generated wallet immediately and abandon the use of any previously created, potentially compromised accounts.

## Operational Continuity Measures

By halting the chain on Sunday, the project successfully contained the breach and prevented additional unauthorized transfers. The rapid response from the Computors allowed for a controlled restart once the software patch was verified. This event underscores the critical importance of secure entropy sources in client-side wallet software for blockchain ecosystems.

## Long-term Security Implications

This incident highlights the systemic risks associated with predictable random-number generation in decentralized applications. Moving forward, the Qubic team must prioritize rigorous audits of their cryptographic implementations. The success of the recovery plan remains a pivotal test for the network's governance model and its ability to maintain user trust following significant security failures.

## Sources covering this story

- https://cointelegraph.com/news/qubic-restarts-blockchain-opens-recovery-claims-after-14m-hack?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._
