Key Highlights:
- Hardware wallet manufacturer Trezor suffered a data breach via third-party logistics partner Skladon, exposing details from approximately 27,000 orders placed between August 9 and November 7, 2026.
- Due to a 90-day anonymization policy, Trezor cannot directly email a subset of affected customers whose orders were placed between August 9 and August 14, forcing reliance on public notices.
- Exposed records contain customer names, phone numbers, postal addresses, emails, order dates, and purchased device models, prompting urgent warnings regarding targeted phishing and physical security threats.
Security Breach at Logistics Partner Skladon Compromises Customer Order Records
Hardware wallet manufacturer Trezor is dealing with the fallout of an unauthorized intrusion at Skladon, an external logistics fulfillment partner. The security incident dates back to November 7, but Skladon did not notify Trezor until November 15—leaving an eight-day window before Trezor could initiate its response. Following the disclosure, Trezor informed relevant data protection authorities and began dispatching direct warning emails to impacted buyers across multiple jurisdictions.
According to official statements, the scope covers months of logistics records. “We believe the attacker exported data for approximately 27,000 orders placed between 9 August and 7 November 2026. An investigation is ongoing,”
the post states. Calculated across the 91-day span, the total volume represents approximately 297 customer orders per day. While the disclosure does not confirm whether the intruder extracted every transaction or merely a portion during that period, Trezor noted that the figures remain provisional pending the conclusion of Skladon’s internal forensics.
The Data Anonymization Paradox: Why Some Customers Cannot Be Emailed
The breach has highlighted an operational paradox embedded in Trezor’s data retention architecture. Under Trezor’s standard protocol, customer order information is kept for a 90-day lifecycle before undergoing anonymization. Because an order submitted on August 9 hit the exact 90-day threshold on November 7—the day the unauthorized export occurred—the earliest records had already been scrubbed from Trezor’s direct internal mailing lists.
Consequently, Trezor disclosed that a “small number of customers who ordered between 9 and 14 August may also be affected, but we can’t email them: their details had already been anonymized in our systems.”
Unable to issue targeted electronic warnings, the company has had to rely entirely on its official public blog and its account on X to alert these early buyers. Rather than prolonging data retention to widen future communication channels, Trezor announced it will aggressively reduce its order-data retention window from 90 days down to 45 days. Under this revised 45-day timeframe, a comparable vendor breach would expose roughly 13,400 orders instead of 27,000, cutting potential third-party exposure in half.
Exposed Personal Information and Escalating Physical Safety Concerns
The sensitivity of the compromised records poses risks that extend far beyond standard credential stuffing or generic spam. The exported database fields include customer full names, contact telephone numbers, physical shipping addresses, email addresses, order timestamps, and the specific hardware models and prices purchased. Possessing granular transaction histories—such as knowing an individual purchased a flagship Safe 5 device on a specific date for an exact dollar amount—arms malicious actors with the precise leverage needed to craft hyper-convincing impersonation scams.
Trezor issued an explicit warning regarding these vectors: “If your data was affected by this breach, scammers may use these details in calls, texts, emails or letters. Please be alert to potential risks to your physical security.”
Reaffirming its fundamental operational boundary, the company stated that “Trezor will never call you or ask for your wallet backup.”
Unlike typical corporate data leaks, the inclusion of residential postal addresses tied directly to cryptocurrency custody devices presents unique physical security vulnerabilities. “Because the data includes your address and what you bought, be careful about who knows you own crypto,”
the company emphasized, advising that anyone who encounters direct intimidation should “contact your local police first.”
Several customers have already reported receiving fraudulent communications attempting to leverage the leaked details.
Supply Chain Challenges and the Expansion of Anonymous Pickup
To systematically eliminate home address exposures, Trezor has accelerated the deployment of its Anonymous Pickup delivery mechanism. This option allows customers to route shipments directly to automated parcel lockers or commercial pickup points rather than their residential residences. While currently active across 18 European nations, an intended rollout in the United States remains pending, leaving the hardware wallet industry’s largest consumer base dependent on traditional shipping channels for now.
Even with privacy-oriented routing, fulfillment partners inherently require a contact number, recipient designation, and delivery location to complete transit. Trezor is conducting a top-to-bottom security review of its third-party service providers and their mandatory contractual baselines. The manufacturer addressed the recurring nature of vendor-level breaches frankly: “We know this is not the first time customer contact details and addresses have been exposed in an incident involving one of our partners,”
offering an apology to customers facing repeated exposures.
This incident follows an earlier breach disclosed in September, when logistics vendor ShipMonk compromised the personal information of 67,000 U.S. customers. While the ShipMonk event concentrated strictly on domestic accounts, Skladon serves as a multi-country distribution hub, extending the geographic dispersion of the current incident. These data leaks also contrast with supply chain tampering risks identified earlier this month, when Trezor uncovered illicit hardware implants in three out of 48 examined Safe 5 units, prompting the vendor to sever ties with roughly 80% of its authorized reseller network.
Why This Matters
The Skladon security incident underscores the vulnerability of decentralized finance participants to centralized Web2 supply chains. While hardware wallets provide robust offline protection for private cryptographic keys, the logistical infrastructure required to manufacture, warehouse, and ship physical devices relies on third-party vendors whose security postures frequently lag behind the products they handle. Leaking physical addresses alongside hardware wallet purchase confirmations turns self-custody advocates into identifiable targets for extortion, targeted SIM-swapping, social engineering, and residential burglary. As hardware wallet manufacturers navigate third-party vendor risks, the reliance on automated collection lockers, shorter data retention windows, and minimized metadata collection will become an indispensable operational standard across the crypto hardware sector.
Frequently Asked Questions
What customer data was compromised in the Trezor Skladon breach?
The exported records include customer names, email addresses, phone numbers, delivery postal addresses, order dates, and details regarding the specific hardware products purchased and the amounts paid.
Were cryptocurrency funds or private wallet recovery seeds compromised?
No. The breach occurred within an external logistics fulfillment database maintained by Skladon. It did not compromise Trezor’s core firmware, software, or customer private keys. Trezor reminds users that it will never call customers or request wallet recovery backups.
Why are some affected customers not receiving direct email notifications?
Trezor automatically anonymizes customer order records once they reach 90 days of age. Because orders placed between August 9 and August 14 had already passed this threshold prior to Trezor receiving notification of the breach on November 15, their contact details were already erased from internal customer support databases. Those individuals must rely on Trezor’s official blog and social media notices for incident updates.




