Keystone to Destroy 18,835 Wallets After Device-Authentication Key Theft
- Published
- Updated
- Since then
- 9 new reports
- Also mentions
- BTC
Keystone is destroying 18,835 unsold hardware wallets after a website breach exposed a device-authentication key used to verify its products. The incident also touched customer records, and the company has paused direct shipments while it replaces the key at the factory level.
Key claims & sources
What it means
Owners who received a device after October 20, 2026 can no longer trust Keystone's own online check and must run additional authenticity verification, even on units that pass the portal test. Keystone is junking all 18,835 unsold wallets in its inventory rather than risk shipping units tied to the compromised key, and direct web orders are frozen until the key is replaced at the factory. New buyers wait longer; existing old-key holders carry the burden of proving their device is real.
A non-custodial wallet's whole appeal rests on the user controlling their keys, but the authenticity system guarding against counterfeits is centralized in a single factory-burned credential Keystone cannot revoke or rewrite remotely. That single point of failure now undercuts the device's core promise, even though Keystone says recovery phrases and private keys themselves were untouched. The separate finding that buyer data sat past the firm's own 180-day deletion policy, missed by an automated tool, adds a privacy lapse that has nothing to do with cryptography.
The outstanding question is how fast Keystone completes the factory-level reissue of the WebAuth key and resumes direct shipments, which remain paused as of the October 26 disclosure. Equally unresolved is what permanent verification process replaces online checks for the already-shipped old-key devices, since Keystone has only described extra scrutiny as an interim fix. How the company handles the 25,964 exposed buyer records, some retained beyond its stated policy, will also test its data-handling credibility.
Market reaction i
Coverage timeline
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 | Loopscale Lending · Unknown incident | no figure in dollars |
| 1 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 1 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 3 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
| 4 days ago | Solana MEV Bot King · Hot wallet key compromise incident | $856k |
4280 incidents stored