SlowMist Says Qubic Wallet Keys Could Be Recovered From Six Network Samples
Published
SlowMist linked the Qubic wallet theft to weak randomness in seed generation, and The Defiant reported that a 4.26.4 patch separates new account seeds from an exposed random stream while leaving header generation unchanged. The two reports point to a security fix that changes part of account creation while leaving another part intact.
What this rests on
What it means
Qubic is the system at the center of a wallet security issue that was examined by SlowMist and then tied to a software update described in The Defiant’s coverage. Seed generation is one of the most sensitive parts of a crypto wallet, because it determines how accounts are created and how keys are formed. A patch that changes seed handling while preserving other generation steps shows the issue sits inside account-creation logic, not in every part of the product.
For users and builders on Qubic, the immediate practical question is how wallet keys are produced and which parts of the creation flow still rely on exposed randomness. If new account seeds are now separated from that stream, wallet operators and developers have to work with a changed generation process and check what remains unaffected. Existing account holders also have to know whether the fix applies only to new accounts or reaches older ones as well. (per thedefiant.io)
The case puts a familiar crypto trade-off in view: systems that promise strong key security depend on implementation details that are easy to get wrong and hard to spot from the outside. A weakness in randomness can undermine the basic promise of self-custody, even when the rest of the network looks normal. It also shows how partial fixes can narrow one attack path while leaving adjacent code paths in place.
Still open is how far the 4.26.4 change goes in practice and whether any other wallet-generation paths on Qubic remain exposed. The next useful detail would be a full technical account of what the patch changes, which versions it covers, and whether the earlier theft matches the same weakness in every affected sample. Until that is clear, the scope of the fix remains the key unknown.
Market reaction
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | AlpsCon AI Trade Hub · Incorrect Share Accounting incident | $152.8k |
| 1 days ago | Argent-style Smart Wallet System · Smart contract vulnerability incident | $59.8k |
| 2 days ago | Coffer · Rounding Error incident | $1 |
| 3 days ago | Qubic · Weak Key Generation incident | $1.3M |
| 5 days ago | KolanHook (1.279453 ETH) incident | no figure in dollars |
4208 incidents stored