Trezor's 27,000-Order Breach Leaked Addresses, Not Keys. That's Still Bad.
A shipping partner exposed names, phone numbers, and home addresses tied to roughly 27,000 Trezor orders. No seed phrases, no PINs, no drained wallets. But a scammer holding your order history doesn't need your keys to ruin your month, and the hardware wallet industry's weakest link just got exposed again.
Twenty-seven thousand orders. Names, phone numbers, email addresses, home addresses, and the exact hardware wallet someone bought. That's the haul from a breach at Trezor's shipping partner, and it's the kind of dataset that makes a scammer's job embarrassingly easy.
Here's what didn't leak: recovery seeds, PINs, passphrases. Nobody's bitcoin moved because of this. That distinction matters, and it's already getting flattened by people shouting "Trezor got hacked" into their timelines.
What actually happened
Skladon, the logistics firm handling Trezor's fulfilment, told the hardware wallet maker on November 15 that someone had unauthorized access to its systems. The intrusion itself dated to November 7. So there's an eight-day gap between the break and the heads-up, which isn't enormous by breach-disclosure standards but isn't nothing either.
The records covered orders placed between August 9 and November 7, roughly 27,000 of them. What was bought, who bought it, where it shipped. Trezor says a small number of earlier August customers may be in the mix too, even though their details had been anonymized inside Trezor's own systems before the notification went out.
Admittedly, "anonymized" is doing a lot of quiet work in that sentence. Strip a name off an order and you still have a street address and a specific device model. That's often enough to re-identify somebody, which is the sort of thing privacy researchers have been saying for years while everybody nodded and then kept the spreadsheet.
Trezor's response: contact affected customers where it still can, notify a data-protection authority, and roll out or expand anonymous pickup at collection points across much of Europe so future orders never put a home address into a warehouse database at all. Plus a retention cut, from 90 days to 45, with more trimming under consideration.
The weak link was never the chip
Hardware wallets are, genuinely, the most defensible way to hold your own keys. The secure element does its job. Firmware signing does its job. And then the box gets handed to a courier, and the whole security story quietly depends on a third-party warehouse in another country, run on a tight budget, storing a record of who owns what and where they sleep.
That's the part this industry has been slow to internalize. A decade of hardening the cryptographic layer, and the exposure still ends up living in a fulfilment database with a login page.
The immediate risk isn't theft of funds. It's impersonation. Hand a competent scammer your name, your address, and the fact that you bought a hardware wallet last month, and they can write a message that clears every mental filter you've. It references a real order. It has a plausible tracking number. It lands when you're actually expecting a parcel.
Which raises the harder question. The question worth asking: how many of those 27,000 people bought that device precisely because they were worried about security, and now have their home address in somebody else's hands?
Physical security is the bit nobody in this sector wants to discuss. A criminal who believes a household holds serious crypto doesn't need to crack a chip. They need a door. Granted, most of the 27,000 will never hear from anyone. But "most" isn't a security model.
What to do, and what it tells us
If you're inside the affected window, assume targeted contact is coming eventually. Calls, texts, letters, a fake support portal with your order number pre-filled. None of that makes the sender legitimate. Verify through a site you typed in yourself, not a link inside the message. Never type a recovery phrase into a form, and never read it to a caller, and yes, that includes the very polite person who already knows your order number and your postcode.
Now the part that should sting. Trimming retention from 90 days to 45 is the right move. It's also a fix that should've existed years ago, and 45 days still means a breach six weeks from now leaks the last six weeks of buyers. I'm not entirely convinced the number should be a number at all. Delete the address once the parcel scans as delivered. Keep the invoice, drop the home address.
As for who wins, it's the privacy-first checkout tools and the compliance vendors who are about to get a very interested phone call from every hardware manufacturer with a European customer base. Who loses? Trezor's support team, for months, fielding calls from people who genuinely can't tell whether the voice on the other end is them.
And the skeptics who call hardware wallets overkill will grab a small rhetorical win from this. To be fair, they're still wrong about the device. But they're right that buying one isn't the end of your operational security. It's the start of it, and your vendor's supply chain is now part of your threat model whether you like it or not.
One more thing worth sitting with. Every one of these incidents gets filed under "third-party vendor" in the disclosure, and every one of them lands on the customer's doorstep. Literally, in this case.
So here's the takeaway. Your seed phrase was never the thing at risk this time. Your address was. Treat the second one with roughly the same paranoia you give the first, because a scammer holding your order history doesn't need your keys to make your week very bad.
Explore More
Key Terms Explained
Coinbase's Layer 2 blockchain built on the OP Stack (Optimism's technology).
The first cryptocurrency, created in 2009 by the pseudonymous Satoshi Nakamoto.
Following the laws and regulations that apply to financial activities, including crypto.
A physical device that stores cryptocurrency private keys offline.