Qubic wallet drain: weak seed generation, 1,404 wallets

About 2.94 trillion QU from 1,404 wallets, per Qubic, which says 87.1% never left the network and the 12.9% sent to MEXC was frozen; funds moved to escrow for reclaim. No USD figure from Qubic.

Root cause: Per Qubic: 'Some wallet seeds were generated with insufficient randomness'; the issue was in seed generation, not the protocol. The fix replaces Math.random() with crypto.getRandomValues() (per the commit and BlockSec Phalcon). Qubic's full technical report is pending.

Timeline, as sourced: Drain 17 Oct 2026 23:42 UTC to 18 Oct 01:26 UTC (per Qubic); fix committed 18 Oct 03:28 UTC (GitHub); Qubic update 18 Oct 12:29 UTC; network resumed and reclaim opened 20 Oct (per Qubic).

Between 23:42 UTC on 17 October and 01:26 UTC on 18 October 2026 an attacker drained 1,404 Qubic wallets, about 2.94 trillion QU, according to Qubic's incident update (opens in a new tab). Qubic says some seeds were generated with insufficient randomness (opens in a new tab) and that the issue was in seed generation, not the protocol; affected seeds are those created on an iPhone or iPad in any browser or on a Mac in Safari before 18 October 2026, or in the Qubic iOS app before July 2025. Computors halted the network, and Qubic says 87.1% of the drained funds never left it, while the 12.9% sent to MEXC was frozen there. The wallet's fix commit (opens in a new tab) replaces Math.random() in seed generation. BlockSec Phalcon (opens in a new tab) says the weakness was reported as early as February. SlowMist (opens in a new tab) separately found that the same Math.random() stream fed values visible in network packet headers, and that its proof of concept recovered keys from six consecutive observations, with real-world exploitability depending on other factors. On 20 October Qubic said (opens in a new tab) the quorum had approved a recovery, the network was live again and a reclaim platform was open until 1 May 2027; it told web wallet users to treat any wallet created before version 4.26.4 as insecure (opens in a new tab). A full technical report is pending.