Qubic suffered a wallet drain in which an attacker emptied 1,404 user wallets of approximately 2.94 trillion QU tokens, valued at roughly $1.3–1.4 million. The theft occurred between 23:42 UTC on October 17 and 01:26 UTC on October 18, 2026, lasting about 104 minutes. Validators known as Computors halted the mainnet at tick 85,371,949, freezing the bulk of the stolen funds. About 87.1% of the drained QU remains immobilized on-chain, while the remaining 12.9% reached MEXC, which froze the receiving account within roughly one hour.
The incident is attributed to weak, predictable wallet seeds rather than a flaw in the Qubic protocol itself. Developers released client version 4.26.4 to correct seed generation and secured additional exposed funds before they could be taken. QEARN staking was unaffected. Exchanges including MEXC and Bitget suspended QUBIC deposits and withdrawals. Recovery options for affected users will be decided by a vote of the Computor quorum.
The Drivers of the Current Situation
The main issue is the rapid drain of 1,404 wallets via insufficient randomness in seed generation on certain Apple devices, Safari browsers, and earlier versions of the Qubic iOS app. Seeds created in any browser on an iPhone or iPad, Safari on Mac (through October 18, 2026), or the iOS app before July 2025 were vulnerable because they relied on JavaScript’s Math.random() rather than a cryptographically secure method. The attacker reconstructed predictable seeds and withdrew funds; the network protocol itself was not compromised.
Related factors limited further losses. Validators acted quickly to pause transactions, trapping most of the stolen tokens on-chain. MEXC’s rapid freeze of the inbound account contained the portion that left the network. The project patched the generation process in version 4.26.4 by switching to crypto.getRandomValues(). Only the observed drain figures, the network halt, and the freeze percentages are confirmed in official updates. Broader confidence in the response has centered on the containment of funds and the absence of impact on staking.
Continued monitoring requires observation of the Computor vote on recovery, network restart timing, and any merchant or user reaction data. Limited immediate disclosure on the exact recovery mechanism forms a narrower path for precise forecasting. The project and exchanges are actively managing the aftermath. The situation is a wallet-seed exploit that left the majority of stolen tokens frozen while the network remains paused.
Impact and Broader Context
Questions about the Qubic hack that left roughly $1.4 million in stolen tokens frozen keep growing. The freeze creates uncertainty about how and when victims will be compensated. It also elevates attention on the risks of weak client-side randomness in wallet software. Users, exchanges, and competing networks continue to assess the implications.
The issue drives debate on seed-generation security across blockchain wallets. It raises questions about the durability of user funds when randomness is inadequate, the limits of rapid network intervention, risks of similar client-side flaws elsewhere, effects on near-term confidence in Qubic, and competition among recovery approaches. Official statements stress that the protocol itself was not at fault and that most funds were contained. Coverage notes that the halt and freezes occurred within hours of the attack window.
The mid-October drain forced renewed focus on wallet security practices. The current review shows how subsequent Computor decisions, network restart, or further technical disclosures will determine the lasting effect.
New recovery-plan details, updated on-chain metrics, or additional security actions will clarify the final disposition of the frozen tokens.
This analysis uses Qubic’s official incident updates and contemporaneous reporting. Fund recovery outcomes and network restart timing remain subject to the Computor quorum decision and market conditions.