Trezor, one of the best-known makers of hardware wallets for storing cryptocurrency offline, has confirmed that customer data was exposed through a breach at a shipping partner. The company disclosed the incident but has not yet detailed exactly which categories of information were affected.
Hardware wallets like Trezor’s are designed to keep private keys off internet-connected devices, reducing exposure to remote hacking. But the physical nature of the product means customers must supply shipping details, including names and addresses, to receive their devices. That data lives with logistics partners outside Trezor’s direct control, creating a separate attack surface.
Third-party breaches of this kind are a recurring risk across e-commerce, not unique to crypto. What makes them notable in this sector is the nature of the customer base. Anyone whose address is linked to a hardware wallet purchase can be inferred to hold cryptocurrency, making that information valuable to scammers and, in rarer cases, to those planning physical theft or extortion.
Trezor has built its brand around security and self-custody, positioning its devices as a safer alternative to keeping funds on exchanges. A breach involving a partner rather than Trezor’s own systems does not compromise the cryptographic security of its wallets. It does, however, expose customers to secondary risks that have nothing to do with the hardware itself.
The company has not specified how many customers are affected or which regions the shipping partner served. Details about the timeline of the breach, when it was discovered, and when affected customers were notified have also not been made public at this stage.
Crypto companies handling physical products have increasingly relied on outside vendors for fulfillment, warehousing, and delivery. Each additional vendor relationship expands the pool of systems that could be targeted by attackers looking for data tied to cryptocurrency holders. Security researchers have long warned that supply chain partners, rather than the primary company, are often the weakest link in data protection.
For now, the practical advice for affected customers centers on vigilance rather than any change to how their devices function. Recipients of unsolicited messages referencing a Trezor purchase should treat them with suspicion, since exposed shipping data can be used to craft convincing phishing attempts.
Sources disagree on this story
This article was published before the reports below were compared. The reporting above stands; what follows is where the published accounts do not agree.
CryptoBriefing reports that no official Trezor confirmation of the 13,689-customer breach exists, while four other outlets cite a specific Trezor statement and security notice detailing the incident.
What all sources agree on
- The breach involved a shipping/fulfillment partner (identified as ShipMonk by Decrypt, crypto.news, and Finbold) and affected 13,689 customers.
- 11,742 customers had full names, phone numbers, email addresses and shipping addresses exposed; 1,947 had partial data (names, cities/emails) exposed.
- Affected customers were in the US, UK, Sweden, Colombia, Brazil, Italy and Portugal, having received orders within 90 days prior to August 8, 2026.
- Trezor's own systems and hardware wallets were not compromised.
- The incident marks the first time in Trezor's history that a breach exposed customer phone numbers and shipping addresses.
- Trezor is developing an Anonymous Delivery option in response.
Where the reports disagree
1Whether Trezor has officially confirmed or communicated about the breach
Notably, no official confirmation or detail about the breach affecting 13,689 users has surfaced in major news outlets or Trezor's own communications as of August 13, 2026.
Trezor said in an Aug. 13 security notice that ShipMonk informed the hardware wallet maker on Aug. 10 about unauthorized access to systems containing customer order data, with an investigation into the incident still underway.
the company disclosed on Thursday.
According to a message Trezor shared on X on August 13, ShipMonk notified the company on August 10 that an unauthorized party had gained access to customer data.
What would settle it: Trezor's own public statement, security notice, or X post dated August 13, 2026, and any archived version of Trezor's official communications.
What to make of it
Treat the core breach figures (13,689 customers, the split between full and partial data exposure, and the affected countries) as consistently reported across four outlets. Do not treat CryptoBriefing's claim of 'no official confirmation' as settled, since it directly conflicts with other outlets' citations of a named Trezor statement and security notice dated August 13.
Market Impact
The breach is unlikely to have a direct effect on cryptocurrency prices, since it involves customer data rather than any protocol, exchange, or custody failure. Its more relevant impact is reputational, touching on trust in hardware wallet vendors that market themselves as the secure alternative to exchange-based custody.
Investors and users may pay closer attention to how crypto hardware companies vet and monitor their logistics and fulfillment partners going forward. Incidents like this tend to accelerate industry-wide scrutiny of vendor security practices, particularly among companies whose customer lists double as a map of cryptocurrency holders.
Further details from Trezor about the scope and timeline of the breach are expected as the company continues to investigate the incident with its shipping partner.
Frequently Asked Questions
What happened in the Trezor data exposure?
Trezor confirmed that customer data was exposed after a breach at one of its shipping partners, though full details on the scope have not been released.
Were customers' cryptocurrency funds or private keys at risk?
There is no indication that private keys or wallet security were compromised. The exposure reportedly involved customer data held by a shipping partner, not Trezor's device security.
What kind of information was exposed?
The exact categories of exposed data have not been specified, but shipping-related breaches typically involve names, addresses, and order details.
What should Trezor customers do now?
Customers should be cautious of unsolicited messages referencing their purchase, as exposed shipping data can be used for targeted phishing attempts.