Back to all articles

Keystone WebAuth key stolen: when hardware wallet authenticity checks can no longer be trusted

Share

Could a stolen verification key let a counterfeit hardware wallet pass as genuine? That is the risk highlighted in Keystone's 26 October 2026 statement. Following unauthorized access to its online store detected on 20 October, the manufacturer reported that an attacker had obtained customer records and the WebAuth key used by its device-authenticity check.

Keystone plans to destroy 18,835 unsold wallets carrying the key, provision future devices with a replacement key and pause affected shipments. No counterfeit Keystone using the stolen key, or theft of customer funds attributable to it, has been publicly confirmed. The possible attack is important, but a theoretical capability is not evidence that it has been exploited.

Timeline: a customer-data breach became an authentication incident

Keystone provided the following sequence:

  • 20 October 2026: the company detected unusual access to its website and says it blocked access paths and disabled sensitive functions that day.
  • 23 October: after reviewing Shopify-related API activity, it confirmed that a third party had obtained shipping information.
  • 24 October: it first publicly disclosed the customer-data breach.
  • 26 October: the company expanded its disclosure to include the stolen WebAuth key, attributing the privilege escalation to a vulnerability in an unnamed third-party data monitoring tool.
  • 27–28 October: additional verification guidance remains essential for devices received after 20 October, while some operational questions remain unanswered.

According to Keystone, 25,964 buyer records dating from 2024 to 2026 still contained names, contact information, delivery addresses and order details. A further 12,873 unpaid-checkout records contained some personal details. Keystone also acknowledged that its automated erasure process had failed to delete all data within its advertised 180-day retention period. It says it is correcting the process and moving toward a 90-day retention period.

These are company-reported figures, not the findings of an independent forensic audit. Separately from the device risk, exposed shipping addresses and purchase histories create opportunities for convincing, targeted phishing.

What exactly is the WebAuth key?

Keystone's official device verification page describes a QR-code challenge: the owner scans a code with the hardware wallet, enters the response shown by the device, and receives a verification result.

The published Keystone 3 firmware implementation shows cryptographic challenge processing, including an RSA private-key component held by the device. The purpose is to establish that the device possesses a secret provisioned through the legitimate manufacturing process.

If an attacker obtains the key needed to answer that challenge, a counterfeit may be able to produce an accepted response and appear genuine despite having untrusted hardware or software.

The WebAuth key is not a wallet recovery phrase or a transaction-signing key. Keystone says the key is unrelated to seed generation, private-key derivation and transaction signing. The company also says its separate firmware-signing key was not compromised.

That distinction is essential: the reported key theft does not prove existing wallet private keys were exposed, and a counterfeit device remains a potential attack scenario, not an independently verified finding.

Why destroy 18,835 wallets?

Keystone says the WebAuth key is provisioned at manufacture into write-once storage, so existing devices cannot simply be updated with a new key.

The company therefore plans to destroy 18,835 units in inventory provisioned with the compromised key and to pause pending website shipments until new units with a replacement key are ready. This is an inventory figure, not the number of victims or compromised wallets already held by customers.

What owners and buyers should do

The company's advice is primarily based on delivery date, not just purchase date.

Manufactured and delivered before 20 October. Keystone says such a device can continue to be used if it passes the authenticity check. The manufacturer has not advised a blanket movement of crypto assets solely because of this incident.

Received after 20 October with the old key. An apparent WebAuth success is not sufficient on its own to rule out a counterfeit. Keystone advises owners to contact official support and await confirmation before using the device. As of this article's verification date, the manufacturer has not published a complete self-service method for identifying which key is provisioned in a particular device.

Order not yet shipped. Shipments affected by the change are paused on Keystone's official website. Verify timing and resolution directly through the manufacturer instead of following unsolicited order-update links.

Bought through a retailer or marketplace. Retail channel alone does not rule out exposure. Consider actual delivery date, provenance and Keystone's specific guidance. No exhaustive public map of old-key reseller inventory is currently available.

Type https://keyst.one directly into your browser to find the official support channel, including support@keyst.one. Never disclose a recovery phrase, private key or passphrase to support. If a seed has already been created or imported on a device whose authenticity is uncertain, seek a case-specific assessment before taking actions that might expose that seed further.

Customer records make social engineering more credible

An attacker with purchase and delivery details may impersonate a manufacturer, quote real order information or claim a false recall, refund, address correction or wallet-verification requirement.

Keystone says it will not ask owners to return their wallets because of this incident. Requests to send a device to a new address, enter a recovery phrase online or use a supposed “asset migration” service should be treated as suspicious.

Good general practice includes using manually entered official addresses, verifying requests through independent channels and never initializing a device of doubtful provenance.

Keystone versus Ledger: two different trust failures

Our earlier article on hardware implants inserted into genuine Ledger devices considered legitimate devices modified after manufacturing.

Keystone represents a different boundary failure: a potentially counterfeit device could pass a cryptographic test meant to identify genuine devices. In the Ledger scenario, provenance does not prove physical integrity after distribution. In the Keystone scenario, the test itself may lose evidentiary value when the underlying secret is compromised.

Both illustrate that cryptographic device checks help, but do not replace controlled purchasing, returns procedures, inventory custody and careful setup. Related reading: how to evaluate hardware wallet risk without abandoning self-custody and why multi-vendor multisig can reduce common-mode dependencies.

What remains unknown

Public information does not establish when the attacker actually obtained the key, where it was stored or how it was protected, whether counterfeit devices are circulating, or which reseller batches still use the old key. The third-party tool has not been identified, and no CVE number or full independent forensic report has been published for the intrusion.

Keystone's general device authentication page still explains a successful check as proof of authenticity. For a post-20-October delivery carrying the old key, however, the incident-specific warning must take precedence over generic product instructions.

GLOV Secure perspective: trust begins before the first signature

Protecting digital assets involves more than selecting a well-known hardware device. Purchase channels, chain of custody, first-use checks, recovery procedures and decisions about who controls each secret are all part of the threat model.

At GLOV Secure, these questions fit into self-custody risk assessments, including security audits and digital-asset custody architecture reviews. Documented receiving procedures and, when appropriate, multi-vendor multisig can reduce correlated risks; neither is a guarantee against every supply-chain attack.

GLOV Solutions editorial analysis — information checked on 28 October 2026. Incident details are primarily based on Keystone's disclosures. No compromise of GLOV Solutions is alleged.

Official sources and independent analysis

Related articles

Back to all articles