Trezor data breach: What hardware wallet buyers should know13 min read2,579 words

Trezor data breach: What hardware wallet buyers should know

The Trezor data breach exposed names, addresses and order details for about 27,000 buyers. Learn what was not exposed and how to avoid follow-up scams.

Trezor data breachhardware wallet securitycrypto phishingthird-party data breachBitcoin wallet safety
Trezor data breach: What hardware wallet buyers should know

A Trezor Shipping Leak Is More Than an Address Problem

A hardware wallet is supposed to keep your crypto keys offline. That protection still matters, but it doesn't mean every part of buying or using the device stays private. Shipping records, support systems, and email providers can all store information that ties a real person to a crypto product - information a scammer can use.

Trezor says hackers accessed systems at Skladon, a shipping partner, on November 7 and likely exported records for about 27,000 orders. The exposed information may include customers' names, phone numbers, delivery and email addresses, and the products and prices they ordered. Trezor says its own systems weren't compromised, and wallet backups, PINs, and passphrases weren't exposed.

That distinction is important. The leak doesn't, by itself, let an attacker take control of a customer's coins. What it can do is make targeted fraud feel more convincing - because the scammer can reference real purchases and real contact details. In other words, this is less about breaking into wallets and more about breaking into trust.

What happened in the Skladon breach?

Skladon, a logistics provider that ships some Trezor orders, experienced an intrusion on November 7. Trezor says the attackers likely exported records related to approximately 27,000 orders placed between August 9 and November 7. Skladon notified Trezor on November 15, eight days after the intrusion.

The records reportedly included customers' full names, phone numbers, delivery addresses, and email addresses, along with the products purchased and their prices. That's enough to identify a customer and create a plausible reason for contacting them. It still isn't the same thing as access to a wallet or its cryptographic keys.

Trezor says its own systems were not breached in this incident. It also says wallet backups, PINs, and passphrases were not involved. The company has notified a data protection authority, but it hasn't disclosed how the attackers gained access to Skladon's systems. So the precise entry point - and the full investigation details - remain unclear.

Who may be affected?

This incident relates to orders handled by Skladon, not every Trezor customer. Trezor says Skladon doesn't ship to the United States, so US buyers weren't affected by this specific breach. Customers in other markets should use Trezor's notification or support channels to check whether an order falls within the affected period and logistics flow.

Trezor says it notified affected customers where possible. Some people who ordered between August 9 and 14 may not receive a notification because Trezor had already anonymized their records. No notification doesn't automatically mean a customer's data was exposed - or that it wasn't. The safest move is to check through Trezor's official support channel.

What the disclosure does - and does not - confirm

The number is approximate, and Trezor describes the records as "likely exported." That wording matters. An intrusion and a confirmed download of every listed record are not the same thing. Still, customers should assume exposed information could be in criminals' hands and act accordingly, even while they wait for more specifics about individual records.

The disclosure also doesn't show that attackers obtained access to Trezor devices, wallet software, or customer funds. The known risk is the personal and purchase information held by a shipping partner. That boundary is real - but it doesn't make the leak harmless.

What does exposed order data mean for wallet owners?

An address alone can create privacy risk. Pair that address with a person's name, phone number, email, and proof that they bought a hardware wallet, and the scam becomes much easier to pull off. A caller can use exact product or price details to sound like a legitimate support agent or a real delivery company.

The practical risk is this: the data can help an attacker earn trust, but it doesn't authenticate them. If a message includes convincing purchase details, that doesn't prove it came from Trezor. Scammers can use real order info to steer victims toward a fake "security" process - sometimes involving a counterfeit replacement device, a lookalike website, or steps that are designed to collect wallet credentials.

The likely attack is persuasion, not a direct wallet compromise

A hardware wallet protects private keys by keeping them under the owner's control. A shipping record doesn't automatically reveal those keys or let someone authorize a transaction. The attacker usually needs a second step: persuading the customer to reveal a wallet backup, install untrusted software, connect to a malicious site, or approve an action they don't understand.

That's why this kind of breach can still matter even when no passwords or seed phrases were exposed. The order details make the scam feel personal and urgent. A message that says "we know you bought this model" is more persuasive than a generic crypto scam - especially if it arrives while someone is already on edge about the breach.

Trezor says some customers have already reported fraudulent phone calls. The company's materials also point to earlier fake letters bearing Trezor branding, holograms, and QR codes that led to phishing sites. Those examples underline the same lesson: judge the request, not the polish.

A simple test for suspicious contact

Treat unsolicited contact about an order, wallet security, or a "required recovery" as untrusted - even if the sender knows your product model, price, or address. Slow down. Ask what they want you to do. If the request involves disclosing a wallet backup, entering it into a website, or sending it to a person, that's a major warning sign.

A convincing logo, a familiar order detail, or a caller who knows your name doesn't change the rule. Stop the conversation and verify through Trezor's official support channel - reached independently, not through a link, phone number, or QR code supplied in the message.

How does this fit the earlier Trezor incidents?

The Skladon breach is the third reported incident involving a Trezor third-party provider in a little over three months. It's not necessarily that one breach caused the next. The real issue is that customer information can sit across multiple providers, each with its own systems, access controls, and retention practices. From a customer's standpoint, the security boundary includes the whole chain of services.

In August, logistics provider ShipMonk disclosed a breach affecting Trezor-related records. An updated investigation found data for another 67,000 US buyers from 2019 to 2021 that ShipMonk had retained despite assurances it had been deleted. The reported total reached 80,689 people. That episode showed a different risk than Skladon: old records can stay exposed long after the order is done.

In September, an incident at email provider Brevo led to the export of 347,149 email addresses, according to Trezor. Attackers used Trezor's legitimate email channel to distribute a fake security warning that urged recipients to install an app requesting wallet backups. A message delivered through a real company channel can still include a malicious request if the sending provider or account is abused.

The wider history changes the real question

Trezor has also dealt with a Mailchimp insider attack targeting its users in 2022, and a 2024 breach of an external support portal that put contact details for up to 66,000 people at risk. These incidents aren't the same in cause and scope, so they shouldn't be treated as one single technical failure. Together, though, they make a harder question unavoidable: how much customer data does each provider need, and for how long?

Outsourcing is normal, especially for international sales. A logistics business may need a delivery address; an email provider may need an email address. The problem isn't using vendors. The problem is whether data access is limited to the task, whether old records are deleted on schedule, and whether a breach is detected and reported quickly enough to reduce damage.

Customers can't audit every provider in a supply chain. Still, it helps to recognize that "the wallet wasn't hacked" and "my personal data may be at risk" can both be true. That avoids both panic about funds and complacency about targeted scams.

What should affected Trezor customers do now?

The right response is careful verification, not panic. The reported data doesn't give anyone control of your wallet by itself, and rushing to "fix" a problem based on an unsolicited message can create the kind of compromise the breach alone didn't enable.

Use these steps:

  1. Treat unexpected contact as unverified. Don't reply to an unsolicited call, text, email, or letter about your order. Don't use contact details, links, or QR codes included in it.
  2. Verify independently. If you want to confirm whether your order was affected, go to Trezor's official support channel yourself. Don't trust a phone number or web address given by someone who contacted you.
  3. Never disclose your wallet backup. Don't type it into a website, app, or form. Don't read it to a caller or "support agent." A request for it is not a safe way to confirm your identity.
  4. Be cautious with downloads and replacement offers. Don't install an app or firmware from an unsolicited message. Confirm any device or security instruction through official support before acting.
  5. Watch for tailored scams. A scammer may mention a model, price, or delivery address. Those details might come from exposed order data - they still don't prove the sender is legitimate.

If you already shared a wallet backup

If you entered or disclosed your recovery phrase, assume your wallet could be compromised. Don't follow instructions from the person who contacted you. Use a trusted, clean device and set up a new wallet with a newly generated backup, then move any remaining assets to it. If you're unsure how to do that safely, get help through official support.

Trezor's disclosure says wallet backups weren't exposed through Skladon. This advice applies if you shared the information separately - by entering it into a site or app, or giving it to someone. Don't share the phrase again while seeking help; support staff should not need it.

If you received no notification

No email isn't a reliable test. Trezor says some records for orders placed August 9-14 may have been anonymized before notification was possible. If you have a relevant order and want clarity, contact Trezor through a channel you find independently.

For US customers, Trezor says Skladon doesn't ship to the United States, so this incident didn't affect US buyers. That doesn't change the basic rule for unexpected crypto-related contact: verify through a trusted channel and never share a recovery phrase.

What should Trezor and its partners change?

Trezor says it's working to shorten order-data retention from 90 days to 45 days and expects shipping partners to follow the same policy. It has also added anonymous pickup at parcel lockers or collection points in 18 European countries, giving customers an option that avoids providing a home delivery address.

These steps address real risks. Shorter retention means order records are available to a provider for less time after delivery. Pickup options can reduce the amount of residential location data tied to an order. But nothing here eliminates every breach. Records may still be needed for returns, disputes, legal requirements, or operational needs - and a pickup option won't fit every buyer.

Retention rules only help when they're enforceable

The ShipMonk incident shows why "we delete records" isn't enough. Records reportedly stayed available for years despite assurances that they had been deleted. A workable retention policy needs a clear schedule, someone responsible for enforcing it, and a way to verify deletion across production systems, backups, and vendor environments where relevant.

The details will vary by provider and legal obligations. The operational standard shouldn't be abstract. It should define what data is collected, how long it's needed, and how it's removed or anonymized when that time ends. For companies working with vendors, deletion and incident-reporting requirements have to be built into the relationship, not treated like informal expectations.

Vendor security is part of product security

Trezor's explanation is straightforward: a company with global reach can't realistically run every part of distribution itself. That's true for a lot of businesses. Moving everything in-house isn't automatically safer - it can add cost and complexity without guaranteeing better controls.

So the useful question isn't "Should companies use third parties?" It's: what data does each third party receive, what can they do with it, and how quickly will the company know if something goes wrong? A solid vendor setup includes limited access, clear retention periods, expectations for incident notification, and a way to confirm the agreed controls are actually running.

From a customer's point of view, data minimization isn't a theoretical privacy idea. Less data means less fuel for a scam. Trezor's planned 45-day retention and anonymous pickup option are meaningful steps - if they're applied consistently and verified across logistics partners.

Conclusion

According to Trezor, the Skladon incident didn't expose the wallet secrets needed to move customers' crypto. It did expose a different kind of risk: personal data that can make a phishing attempt feel credible. Treat unexpected contact as untrusted, verify through a trusted channel, and never share a wallet backup.

For companies, the broader lesson is operational. Third-party providers are often necessary, but customer data has to be limited to what each task requires, kept only as long as it's needed, and governed by controls that can be checked. That's what turns a supply chain from an invisible risk into something you can manage.

Frequently Asked Questions

Not by itself, based on the information Trezor disclosed. The exposed records reportedly contain contact, delivery and purchase details, not wallet backups, PINs or passphrases. The main concern is targeted social engineering: an attacker may use order information to persuade someone to reveal credentials or take an unsafe action.
Trezor says Skladon does not ship to the United States, so US buyers were not affected by this specific breach. This statement applies to the Skladon incident, not necessarily to other security incidents involving different providers or systems. US customers should still treat unexpected crypto-related messages with caution.
Do not disclose your wallet backup, follow a link, install an app or scan a QR code because a caller asks you to. End the conversation and check the issue through Trezor’s official support channel, accessed independently. A caller’s knowledge of your order or device does not prove their identity.
International order fulfilment involves warehousing, packing and delivery across different regions. Trezor says handling every stage itself is not realistic and that Skladon held information needed to deliver parcels. Outsourcing can be operationally necessary, but the company remains responsible for limiting data access and setting retention and security expectations.

Related articles