Layer-1 blockchain Qubic resumed operations at 8:00 pm on Oct. 19, advancing past tick 85,371,949 after validators approved a recovery plan for the roughly $1.4 million in QU tokens drained from 1,404 accounts, according to Qubic's latest update. The network had been halted since Sunday after an attacker exploited predictable wallet seeds generated by vulnerable wallet software. The project opened a claims platform for affected users with a May 1, 2027, deadline and released web wallet version 4.26.4 to fix the insecure random-number generator that affected wallets created on certain Apple devices and browsers. Qubic warned users who created wallets before the patch to treat them as insecure and migrate funds immediately.

The damage is contained to Qubic's wallet implementation — this was not a protocol exploit, bridge compromise, or shared infrastructure failure. The $1.4 million loss involved no cross-chain collateral or oracle dependencies that could propagate contagion. The network's swift halt prevented further drainage, and the validator-approved recovery plan with a defined claims process indicates functional governance. This is protocol-specific operational risk, not a signal of broader DeFi fragility or an attack vector that generalizes to other chains.

The restart matters primarily to QU holders and users of the Qubic network — no wider DeFi or L1 positioning is implicated. The incident highlights the continued risk in wallet software, particularly around random-number generation on client devices, but does not suggest a new systemic vulnerability in cryptographic infrastructure or cross-protocol attack surfaces. The claims process and timeline provide a known resolution path, removing uncertainty for affected users. For traders outside the Qubic ecosystem, this is a reminder that wallet security remains an operational choke point, but it does not alter the risk profile of major assets or established DeFi protocols.

Watch for any indication that the patched random-number generator still produces predictable seeds — if further drains occur post-restart or if other projects report similar wallet vulnerabilities, client-side wallet risk becomes a broader positioning concern. Until then, this is isolated protocol cleanup with no cross-market transmission mechanism.

Source: CoinTelegraph