Qubic Wallet Security, Explained Plainly
Security isn't a page you write once and forget. It's the sum of specific, checkable decisions — how keys are stored, how downloads are verified, how incidents get handled when they happen. Here's exactly how this wallet approaches each of those, in plain language.
Verified by design, not by claim
Every release is built from the open source tree and published on one official channel, with a non-custodial vault encrypted on your device — so nothing on this page has to be taken on faith.
How to install safelyVerify Every Download
Every release of Qubic Wallet is published by the core team from the same open source tree, on one official channel: qubicwallet.io/download and the GitHub Releases page linked from it. This matters because tampered installers are one of the most effective ways attackers steal crypto — a modified wallet can look completely normal while quietly sending your seed to someone else. Sticking to the official download page, and reading the code if you want to go further, is the direct defense against that. Full steps: how to install.
Your Keys Never Leave Your Device
Qubic Wallet is non-custodial. Your seed and vault are encrypted locally using AES-256-GCM, with your password strengthened through Argon2id key derivation — a modern, deliberately slow function designed specifically to resist brute-force attacks. This isn't marketing language; it's the actual cryptographic approach, and it's the same reason no one, including us, can recover a vault if you lose your password. We never transmit your seed or vault contents to any server. We can't access your funds — and neither can anyone impersonating us.
Open Source, Publicly Auditable
The wallet's source code is public on GitHub, under the official Qubic organization. Security researchers, developers, and anyone curious can read exactly how encryption, transaction signing, and vault handling work — nothing is hidden behind a closed codebase. If you don't want to take our word for any claim on this page, you don't have to. Go read the code that backs it.
How We Handle Security Incidents
We believe transparency builds more trust than silence.
In July 2026, the broader Qubic GitHub organization experienced a security incident — a compromised access token led to unauthorized changes in several repositories, including the web wallet and a core infrastructure image.
Was this desktop app affected?
Whether this desktop application was in scope of that incident is not yet confirmed one way or the other — the official postmortem does not mention it either way, and we won't publish an "unaffected" claim without a direct, specific confirmation. This page will be updated the moment that's resolved.
What "Beta" Means Here
Qubic Wallet is currently in beta. That doesn't mean unstable or unfinished — it means active, ongoing development, with security patches released quickly when needed rather than sitting in a slow, infrequent release cycle. Since its first public release in July 2021, the wallet has been maintained continuously, and the nine most recent versions alone include a dedicated security release for an updated crypto library and an upgrade to Argon2id vault encryption — both delivered without breaking existing users' vaults. Beta, in this case, is a sign of attentiveness, not risk.
A Note on Recovery Scams
If you ever see an offer to "recover" a lost wallet for a fee, or anyone asking for your seed to "help" — that's a scam, not a service. No legitimate recovery is possible without your own seed, and no one legitimate will ever ask you to hand it over. The wallet's own documentation states this directly: Qubic will never contact you to ask for your seed. See our recovery guide for what real recovery actually looks like, and how to protect yourself from people pretending to offer it.
Hardware Wallet Security
If you're looking for an extra layer of physical security, Ledger support is available through an official integration — see our hardware wallet compatibility guide for exact setup steps and current status across devices.
Reporting a Security Concern
If you believe you've found a genuine security issue — not a general support question, but a specific vulnerability or unexpected behavior with security implications — report it through official channels with as much detail as possible. Responsible disclosure benefits everyone using the wallet, and we treat these reports seriously rather than dismissively.
Security as an Ongoing Commitment, Not a Checklist
Everything on this page describes a current state, not a finished project. Security in software isn't something you complete once and move on from — it's continuous attention, patching, and honest disclosure as circumstances change. That's the standard we're holding ourselves to, and this page will be updated as that work continues.
Security Summary
- Encryption
- AES-256-GCM
- Key derivation
- Argon2id (m=64 MiB, t=3, p=1)
- Custody model
- Non-custodial
- Release channel
- One official source, every release
- Source code
- Fully open on GitHub
- July 2026 incident
- Desktop app scope not yet confirmed
- Minimum vault password
- 8 characters
Questions About Security?
Check the FAQ for more, or read the full documentation.
