Trezor Shipping Partner Skladon Breached, Exposing Data From About 27,000 Hardware Wallet Orders
Trezor said on Nov. 16 that a Nov. 7 breach at its delivery partner Skladon exposed names, phone numbers, addresses, emails and order details tied to about 27,000 orders placed Aug. 9–Nov. 7, 2026. Wallet backups, PINs and passphrases were not involved, but scam calls are already reported. It is the third Trezor partner incident since August.

Table of Contents
Trezor, the Czech maker of hardware crypto wallets, said on November 16, 2026, that a breach at one of its delivery partners, Skladon, exposed customer data tied to about 27,000 orders. The leaked records include names, phone numbers, delivery addresses, email addresses and what each customer bought. Trezor says its own systems and devices were not compromised and that no wallet backups, PINs or passphrases were involved. Some customers have already reported scam calls. This is the third incident at a Trezor third-party provider since August.
What happened: the facts Trezor has confirmed
According to Trezor's blog post, dated November 16, Skladon told Trezor on November 15, 2026 that someone had gained unauthorized access to its systems holding Trezor customer shipping data. Trezor says the breach itself happened on November 7, which means eight days passed between the intrusion and the notice to Trezor.
Trezor says it believes the attacker exported data for about 27,000 orders placed between August 9 and November 7, 2026. The company says an investigation is ongoing.
The exposed data, according to Trezor, includes:
Full names
Phone numbers
Delivery addresses
Email addresses
Order date and details, including the product name and price
Trezor also posted about the incident on X on November 16 at 16:18 UTC (19:48 Tehran time). In replies under that post, the company said billing information "was not part of this" and repeated that "Trezor systems were not compromised, and Trezor devices remain secure."
What was not exposed
Trezor says no wallet backups (recovery phrases), PINs or passphrases were involved, and adds that "neither Trezor nor Skladon ever holds them." The private keys stay on users' devices, and the leak does not by itself give an attacker access to anyone's funds.
Who is affected
Trezor says that if a customer received its email about the incident and ordered between August 9 and November 7, 2026, that customer's data was part of the breach. There is one complication: a small number of customers who ordered between August 9 and 14 may also be affected, but Trezor cannot email them because their data had already been anonymized in its own systems under its 90-day data retention policy. Trezor says it is using its blog and X post to reach this group.
Customers who got the email but ordered after November 7 are not affected, according to Trezor. The company says Skladon delivers to many countries, so the incident "isn't limited to one region." Trezor has not published a country list. Decrypt reported that Trezor said Skladon does not ship to the United States, so American buyers were not affected by this incident. We did not find that statement in Trezor's blog post itself.
Why it matters: phishing, social engineering and physical risk
A name and email address are a common phishing target. In this case, though, the attacker also has a home address, a phone number and proof that the person bought a crypto hardware wallet, including the model and the price paid. That combination makes scams look much more believable. Trezor writes that scammers "may quote real order details, including what you bought and what you paid, to make a message look genuine," and that some customers have already reported scam calls.
Trezor specifically warns about risks to physical security. Because the data shows where someone lives and that they probably own crypto, the company advises customers to "be careful about who knows you own crypto" and, if any message contains a threat or makes them feel unsafe, to "contact your local police first."
This is analysis, not a Trezor claim: these breaches do not let anyone touch funds directly. The danger comes when a user is persuaded to type a recovery phrase into a fake website, fake app or fake form, or to install fake software. According to Decrypt, in the September Brevo incident attackers used exactly that method: they sent a fake security warning through Trezor's legitimate email channel and urged recipients to install an app that requested their wallet backup.
Trezor's response
Trezor says it has done or started the following:
Customer notice: it has emailed every affected customer it can still reach and is informing the August 9–14 group through its blog and X.
Regulator notified: it has informed the data protection authority (Trezor did not name the authority).
Anonymous pickup: customers in 18 European countries can now order with anonymous pickup from a parcel locker or pickup point, so their name and home address never reach Trezor. The company says it is working on a U.S. launch "as soon as possible."
Shorter data retention: it is working to cut how long it keeps order data from 90 days to 45 days, with the aim of going lower.
Partner review: it is reviewing its relationships with third-party partners and the security requirements it places on them.
In an X reply on November 16 at 17:49 UTC (21:19 Tehran time), Trezor said German pickup points release parcels only after checking ID, so an alias does not work there. Orders to Germany use "Discreet Pickup" instead: the recipient's real name is needed, but no home address or phone number is requested, and the parcel is unbranded.
When users asked why an order from the official store went through an outside company, Trezor said on X at 17:01 UTC (20:31 Tehran time): "companies of our size and global reach can't run efficiently without third-party service providers," and that Skladon only holds "what's needed to get your parcel to you."
Trezor also wrote in its blog: "We know this is not the first time customer contact details and addresses have been exposed in an incident involving one of our partners… we're truly sorry."
Background: three partner incidents in about three months
Trezor's own published notices describe a run of third-party incidents in 2026:
August 2026, ShipMonk (shipping): ShipMonk told Trezor on August 10 that its systems had been accessed. The first notice (August 13) listed 11,742 customers with full exposure and 1,947 with partial exposure, for orders sent to the US, UK, Sweden, Colombia, Brazil, Italy and Portugal between May 10 and August 8. Trezor called it the first time since its 2013 founding that customer phone numbers and shipping addresses had been exposed. An update on September 4 said ShipMonk had also kept order data from November 2019 to August 2021, despite giving written assurance that it had been deleted. That added about 67,000 US customers and brought the total to 80,689.
September 2026, Brevo (marketing email): Trezor's September 10 notice, updated September 17, says Brevo confirmed that 347,149 marketing email contacts were exported through its API. Decrypt reported that attackers also used this channel to send a phishing message.
November 2026, Skladon (shipping): about 27,000 orders, as described above.
Decrypt also lists older incidents: a Mailchimp insider attack that targeted Trezor users in 2022, a 2024 breach of an external support portal that put contact details of up to 66,000 people at risk, and fake Trezor-branded letters sent to hardware-wallet owners in February.
Separately, MyTraderBot recently reported on hidden implants in Trezor Safe 5 wallets sold by a reseller. That was a different supply-chain risk and is not connected to the Skladon breach.
Reporting differences
The Block's November 16 article (4:44 PM EST, 01:14 Tehran time on November 17) called this a "Sunday announcement." Trezor's blog and X post are both dated Monday, November 16, while Skladon's notice to Trezor came on Sunday, November 15. The Block also called this the "second" such incident since August, counting only the shipping partners. Decrypt counts three by including the Brevo email incident. Both figures depend on what is counted, and Trezor's own notices support both.
Timeline (UTC dates; Tehran time where the exact time is known)
August 10, 2026: ShipMonk informs Trezor of a breach.
September 2–4, 2026: Trezor learns the ShipMonk breach was larger; total updated to 80,689.
September 10–17, 2026: Brevo incident; 347,149 email contacts exported.
November 7, 2026: Skladon breach takes place (according to Trezor).
November 15, 2026: Skladon notifies Trezor.
November 16, 2026, 19:48 Tehran: Trezor posts on X; the blog post is dated the same day.
November 16–17, 2026: coverage by Decrypt, The Block and Cryptonomist.
What users should do
This is a summary of Trezor's guidance, not investment advice:
Never share your recovery phrase (wallet backup) with anyone. Trezor says no one from the company will ever call you or ask for it. Only enter it on the Trezor device itself, never on a website, app, form or QR code.
Treat any unexpected call, text, email or letter about your order as suspicious, even if it mentions the exact model and price.
Contact support only through trezor.io/support, not through a link, number or QR code in a message.
Use a separate email address for crypto purchases. Trezor recommended this in an X reply.
Consider anonymous pickup in supported countries for future orders.
If you are threatened or feel unsafe, contact local police first.
On device security, Trezor said in an X reply that every Trezor ships without firmware, checks the firmware signature at each startup, and that Trezor Suite checks that the Secure Element is genuine before setup. If a device looks wrong when it arrives, Trezor says not to use it and to contact support.
What to watch
Whether Trezor or Skladon says how the attacker got into Skladon's systems. Trezor has not said yet.
Updates to the number of affected orders or the list of countries. The ShipMonk total grew from about 13,700 to 80,689 after an update.
Any statement from the data protection authority or from Skladon itself.
When anonymous pickup launches in the US, and whether shipping partners actually apply the 45-day retention limit.
New phishing campaigns that use real order details. These usually appear within days of a leak.
Glossary
Hardware wallet: a physical device that keeps private keys offline and signs transactions.
Wallet backup / recovery phrase (seed): 12, 20 or 24 words that can fully restore a wallet. Anyone who has it controls the funds.
Passphrase: an optional extra word or phrase that creates a separate hidden wallet.
Phishing: a fake message or website that tricks someone into giving up sensitive information.
Data retention: how long a company keeps customer data before deleting or anonymizing it.
Third-party / fulfillment partner: an outside company that handles storage, packing or delivery.
FAQ
Are my coins at risk if my data was leaked?
Not directly, according to Trezor. The leaked data does not include recovery phrases, PINs or passphrases. The real risk is being tricked through phishing or social engineering, plus possible physical risks.
How do I know if I am affected?
If you received Trezor's email about this incident and ordered between August 9 and November 7, 2026, you are affected. If you ordered between August 9 and 14, you may be affected even without an email.
Should I replace my device or seed?
Trezor says devices are secure and has not recommended this for the Skladon breach. Moving to a new seed is necessary only if your recovery phrase may have been exposed, for example if you entered it anywhere other than the device.
Sources
Trezor blog, "Data breach at Trezor shipping partner, Skladon" (published Nov 16, 2026): trezor.io
Trezor on X (Nov 16, 2026, 16:18 UTC = 19:48 Tehran): x.com/Trezor; replies at 17:01 UTC (third-party partners), 17:27 UTC (billing), 17:49 UTC (Germany pickup)
Trezor blog, ShipMonk incident (Aug 13, 2026; updated Sep 4, 2026): trezor.io
Trezor blog, Brevo incident (Sep 10, 2026; updated Sep 17, 2026): trezor.io
Decrypt (Nov 16, 2026): decrypt.co
The Block (Nov 16, 2026, 4:44 PM EST): theblock.co
The Cryptonomist (Nov 16, 2026): cryptonomist.ch
Related on MyTraderBot
Trezor confirms hidden implants in Safe 5 wallets sold by CryptoBilis
Luxor confirms Commander breach behind hashrate hijack, blames AI-enabled attack
This article is for news and education only and is not financial advice. Last checked: November 17, 2026, about 03:30 Tehran time.
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





