Weak Wallet Seeds Froze a Chain. Check Yours

On October 18, 2026, the crypto network Qubic paused its own blockchain over a wallet seed generation security failure. Between 23:42 UTC on October 17 and 01:26 UTC on October 18, an attacker drained 1,404 wallets of about 2.94 trillion QU, roughly $1.3 million, and the network's validators halted the chain at tick 85,371,949. The security firm SlowMist published its root-cause analysis on October 20, and CryptoBriefing's report on that analysis lays out the mechanism: Qubic's web wallet built its seeds with JavaScript's Math.random(), a function never meant for cryptography. On paper each seed was a 55-letter string with a space of 26^55 possibilities. In practice the weak generator left an attacker facing about 2^32, small enough to brute-force, and SlowMist says output from the same random stream leaked in plaintext through a request header field, which let the generator's internal state be worked out from as few as six observations.

SlowMist singled out seeds made in Safari on a Mac before October 18, 2026 and in the Qubic iOS app before July 2025, and flagged iPhones and iPads more broadly as the higher-risk group. Qubic shipped web wallet version 4.26.4 the same day, which switches seed creation to crypto.getRandomValues(), the browser's actual cryptographic random source. Validators froze about 87.1% of the stolen funds on-chain, an exchange froze the remaining 12.9%, and a decision on restitution now sits with the network's validator quorum.

Qubic is not a coin NexusPool's solo mining pool touches, yet the same mechanism sits under every Bitcoin, Litecoin, Dogecoin, or Bitcoin Cash wallet you have created: a random source picks your seed, and the wallet rarely tells you which one. You can check yours in a few minutes.

Why Wallet Seed Generation Security Checks Matter More Than Seed Length

A seed phrase looks secure because it is long: twelve or twenty-four words drawn from a fixed list. But the words are only as unpredictable as the process that picked them. A seed generated from a weak source, like a software clock, a predictable JavaScript function, or a flawed hardware random-number generator, can look exactly like a seed generated from genuine entropy while being far easier to guess or reconstruct. Qubic's seeds are the clean example: a format with 26^55 possible values, produced by a generator with only about 2^32 real starting points. A long seed from a weak generator protects you no better than the generator does. SlowMist's finding applies to any wallet: the random source carries the whole security model, and most wallet software never names it.

The Wallet Seed Checklist: Is Your Own Seed at Risk

Work through this with any wallet that currently holds funds, software or hardware, for any coin.

• Where was this seed first generated? If you cannot remember, or if it came from a browser-based or web-hosted wallet rather than dedicated wallet software or a hardware device, treat it as unverified.
• Does the wallet's documentation name its randomness source? Reputable hardware wallets and well-maintained open-source software name a specific source, such as a hardware RNG chip or an operating system's cryptographic API. If you cannot find this stated anywhere, that is itself a finding.
• Was the seed generated inside a mobile browser, an embedded web view, or an older app version you have not updated in over a year? Browser JavaScript offers a non-cryptographic random function as the easy default, and that default is exactly what SlowMist traced the Qubic losses to.
• Has the wallet's maker ever disclosed a randomness or entropy bug? A disclosed and patched bug is a sign of a maker that audits itself. No disclosure ever, for software old enough to likely have had one, is a weaker sign than it looks.
• Have you ever moved this exact seed's funds to a fresh seed generated on current, patched software? If the answer is no and the seed is old, it still carries whatever weakness its original software had, for as long as funds sit on it.

If You Checked "Unverified" or "No" on Two or More

Do not wait. Generate a brand-new seed on current wallet software from a maker that documents its randomness source, move your funds to it in a transaction you control, and retire the old seed completely rather than reusing it as a backup. If every answer above came back clean, your current setup already reflects the practice this incident is pushing the rest of the industry toward, and the useful move is simply to repeat this check whenever you adopt new wallet software, not just after a headline.

None of this is a claim that any particular wallet, including the ones NexusPool's miners use to receive their own block rewards, is flawed. It is also not investment advice, and this checklist does not make finding a block more or less likely. Checking where your keys came from is a different question from whether you find a block: your odds are set by your hashrate against network difficulty, the same way at every pool.

Where NexusPool Fits: Your Rewards Land on Your Own Seed

Self-custody is the point of solo mining. NexusPool's technology page explains why the pool never holds a balance for you to later worry about: a found block's coinbase transaction pays your own address directly, and nothing routes through NexusPool first. You can see that exact coinbase before you ever find a block with the Payout Preflight tool, and once your rig is running, the pool's signed hourly receipts show the shares and difficulty it counted for your work, checked against a key NexusPool publishes rather than taken on faith. None of that replaces the check above. A non-custodial pool still pays out to whatever address your wallet generates, and that address is only as safe as the seed behind it.

Trust nothing. Verify where your own wallet's keys came from.