Hardware wallet maker Trezor has disclosed a third-party data breach affecting approximately 13,689 customers after unauthorized actors accessed systems operated by its shipping and fulfillment provider, ShipMonk.
The incident exposed order-related personal data and poses a significant risk of targeted phishing, social engineering, and potential physical-world fraud against cryptocurrency holders.
Trezor said ShipMonk notified the company of unauthorized access to systems holding customer information on August 10, 2026.
ShipMonk Data Breach
The investigation remains ongoing, but Trezor emphasized that the breach occurred within ShipMonk’s environment, not Trezor’s own infrastructure. The company stated that its devices, products, services, and customers’ wallet backups remain secure.
The incident affected customers in the United States, United Kingdom, Sweden, Colombia, Brazil, Italy, and Portugal. Trezor initially identified orders received between May 10 and August 8, 2026, as being within the affected dataset.
Of the 13,689 affected individuals, 11,742 had their names, email addresses, phone numbers, and shipping addresses fully exposed. A further 1,947 customers had a more limited set of information exposed: name, city, and email address.
Trezor cautioned that this partially exposed group may include older orders and said it is verifying the precise timeframe with ShipMonk. While Trezor’s disclosure focuses on personal and fulfillment data, the operational implications are substantial.
A confirmed hardware wallet owner list, paired with home addresses, telephone numbers, and email addresses, provides a high-value targeting dataset for financially motivated threat actors.
Trezor warned that affected customers could face more convincing phishing attempts across email, SMS, phone calls, and physical mail.
Attackers can use leaked order information to impersonate Trezor support, cryptocurrency exchanges, delivery services, banks, or other trusted organizations.
For example, an attacker could send a victim a message referencing a recent Trezor delivery and claim that a “security validation” is required.
The message may direct the recipient to a cloned Trezor site designed to harvest a wallet recovery seed. Since the attacker may know the victim’s name, address, contact information, and likely device ownership, such lures can appear more credible than generic crypto scams.
Trezor reiterated that users must never enter a wallet backup or recovery seed on any website, in any application, via email, or in support chat. Recovery seeds should never be shared with anyone claiming to represent Trezor or any other service.
Trezor attributed the breach’s limited scope to its 90-day order data retention policy, under which fulfillment partners must delete or anonymize customer data after delivery-related processes, including returns, refunds, and replacements, are completed.
The company said older records were no longer present in ShipMonk systems and therefore could not have been exposed.
However, the update concerning the 1,947 partially exposed customers illustrates a familiar third-party risk-management problem: data-retention requirements are valuable only when they are consistently implemented, verifiable, and auditable across the supplier ecosystem.
The company recommends that you independently verify all Trezor-related communications on its official website, blog, and social channels.
Affected users should treat unexpected support requests, delivery notices, account-verification prompts, and urgent crypto-security alerts as potentially malicious.
They should also monitor email and phone communications closely, use a separate email address for future purchases where possible, and consider privacy-preserving delivery and payment options for hardware-wallet orders.
Detect, investigate, and respond faster with in-browser data inspection from ANY.RUN. Gain complete phishing visibility to strengthen your SOC and reduce MTTR