On November 16, 2026, Trezor disclosed a data breach at Skladon, one of its logistics partners, that may have exposed personal information associated with approximately 27,000 hardware wallet orders. The incident involved names, contact details, shipping addresses, and purchase information, without affecting the manufacturer’s systems or the credentials required to access crypto-assets. This distinction is important, but it does not eliminate the risks to users: information unrelated to the technical operation of a device can be used to carry out targeted scams or identify individuals who may hold digital assets. The case highlights an often overlooked dimension of self-custody, where security depends not only on protecting private keys but also on preserving personal data privacy and ensuring the reliability of the organizations involved in device distribution.
The data breach at the logistics provider
According to Trezor’s disclosure, an unauthorized actor gained access on November 7 to Skladon’s systems containing shipping information. The logistics provider notified Trezor on November 15, and the company publicly disclosed the incident the following day. The data believed to have been exported relates to approximately 27,000 orders placed between August 9 and November 7, 2026, and includes names, phone numbers, email addresses, shipping addresses, purchased products, and their prices. The investigation remains ongoing, and the reported figure is an estimate of affected orders rather than necessarily the number of distinct individuals involved. The breach also spans several countries served by the logistics provider and is not limited to a single national market.
Trezor stated that its own systems were not compromised and that the incident did not involve wallet backups, PINs, or passphrases, none of which are held by either the manufacturer or the logistics provider. There is therefore no indication that devices were compromised or that attackers gained direct access to users’ crypto-assets. The primary concern is the potential use of the exposed information in subsequent fraudulent activity. The company has already received reports of scam calls in which attackers impersonated support representatives, using knowledge of customers’ purchases to make their approaches more credible. The incident demonstrates how a breach outside the custody infrastructure can still create opportunities for attackers, without exploiting vulnerabilities in hardware wallets or their cryptographic systems.
From exposed information to targeted fraud
The value of the exposed information lies primarily in its ability to link an individual’s identity to the purchase of a self-custody device. An email address or phone number does not provide direct access to funds, but it can become a useful tool when combined with the purchased model, order date, and shipping recipient. These details can support apparently authentic communications in which an attacker impersonates the manufacturer and claims that a security issue, software update, or verification procedure requires immediate action. The objective may be to persuade users to reveal their wallet backup or authorize transactions that transfer funds to an attacker. The presence of accurate personal information increases the credibility of these attempts, making legitimate communications more difficult to distinguish from fraudulent ones.
The exposure of shipping addresses also introduces risks beyond digital fraud. Knowing that a particular individual purchased a hardware wallet may suggest ownership of crypto-assets, even though it provides no reliable indication of whether those assets are still held or what their value might be. This association can expose affected individuals to intimidation, extortion, or other forms of pressure, particularly when the information identifies a home address. There is insufficient evidence to attribute physical attacks to the Skladon breach, but the availability of this information represents a risk worth considering. Protecting private keys therefore remains essential, but it does not address every security concern faced by individuals managing their own assets. Preserving the confidentiality of information linking a person’s identity to potential crypto-asset ownership is also part of protecting the user.
Third-party risk management and data protection
The Skladon incident follows other security breaches involving Trezor’s external service providers. In August 2026, a breach at logistics partner ShipMonk affected approximately 13,700 individuals, while a subsequent update identified the exposure of data belonging to an additional 67,000 U.S. customers. The latter records dated back to a previous commercial relationship and, according to Trezor, had been retained by the provider despite repeated assurances that they had been deleted. In September, a compromise affecting the communications platform Brevo allowed fraudulent messages to be distributed through a channel used by Trezor. A subsequent investigation confirmed that 347,149 email addresses had been exported from its marketing communications list. Although these were separate incidents, they highlight a common vulnerability: exposure to cybersecurity risks originating from organizations that process information and provide services on the manufacturer’s behalf.
These repeated incidents draw attention to the importance of managing the entire supplier network. A company may maintain strong security standards for its devices and internal systems while still needing to share certain information with logistics providers, communications platforms, and other service providers. Data protection therefore also depends on partner selection, contractual requirements, and verification that those requirements are actually being followed. Following the latest breach, Trezor announced a review of its third-party relationships and security requirements, along with plans to reduce its order data retention period from 90 to 45 days. The company also introduced an anonymous pickup option in 18 European countries, allowing customers to purchase devices without providing their name or home address to Trezor. These initiatives are intended to reduce the amount of information collected and the period during which it remains available, although their effectiveness will depend on consistent implementation across the supply chain.
Self-custody between autonomy and responsibility
The Trezor case illustrates two dimensions of security that are often considered separately. Self-custody enables users to maintain direct control over their crypto-assets without entrusting an intermediary with the credentials required to move them. This model reduces dependence on a third-party custodian and certain risks associated with centralized asset management, but it also places greater responsibility on individuals for protecting private keys, managing backups, and executing transactions. Autonomy in custody does not, however, mean complete independence from external organizations. Device purchases, distribution, software updates, and support services still involve companies and infrastructure over which users have limited control. Assessing security therefore requires consideration of these dependencies as well, since they can create risks distinct from those directly associated with private key management.
Choosing a self-custody solution consequently requires an assessment that extends beyond the device’s technical specifications. Security architecture, software verifiability, and credential protection remain fundamental, but personal data policies, supplier reliability, and the manufacturer’s ability to prevent and respond to incidents are also relevant. Limiting the information shared during purchases and verifying the authenticity of communications can help reduce individual exposure. Users also differ in their technical capabilities and their ability to manage the operational responsibilities associated with independent custody. The choice between self-custody and professional custody services should therefore consider the different risks, controls, and responsibilities associated with each model, rather than assuming that one approach is universally safer than the other.
Conclusions
The data breach at Skladon demonstrates why self-custody security cannot be assessed exclusively through private key protection and device reliability. The absence of a direct wallet compromise is essential to understanding the scope of the incident, but it does not eliminate the consequences of exposing personal information. The succession of incidents involving different Trezor service providers also highlights the importance of organizational controls and effective third-party risk management. These risks do not diminish the value of the autonomy offered by self-custody, but they clarify its responsibilities and operational limitations. Assessing available solutions should therefore take into account both cryptographic security and the ability of the organizations involved to protect personal data, minimize information collection, and respond effectively to incidents. The decisive consideration is not only who controls the private keys, but also how effectively the information and processes that may expose users to risk are protected.