e2ee9e80-4
Trezor Flags Skladon Breach Tied to About 27,000 Orders
Trezor says a Nov. 7 Skladon breach may have exposed records linked to about 27,000 orders. Wallet seed phrases, PINs and passphrases were not exposed, it said.

Outputs
A Nov. 7 breach at Skladon may have exposed records tied to about 27,000 orders.
Records dating to Aug. 9 may have been exported.
Potential fields include names, phone numbers, home addresses, emails, purchase and payment information.
Trezor said seed phrases, PINs and passphrases were not exposed.
Some customers reported fraudulent calls; this was Trezor’s third partner breach in three months.
By Elena Vasquez
What did the Skladon breach affect?
Trezor disclosed that a Nov. 7 breach at logistics partner Skladon may have exposed records tied to about 27,000 orders. The figure concerns orders, not a confirmed count of individual customers, and Trezor did not provide a record-level breakdown.
Records dating back to Aug. 9 may have been exported, according to the company. The affected fields could include buyers’ names, phone numbers, home addresses and email addresses, along with purchase and payment information.
Combined with order context, those fields can support convincing phishing and impersonation attempts, particularly when a caller already knows a purchase. The disclosure does not establish misuse of payment information, fraudulent charges or unauthorized wallet transactions.
What did Trezor say was not exposed?
Trezor said: “Seed phrases, PINs and passphrases were not exposed.” That statement separates order and contact data from credentials associated with wallet access, but it does not address the separate risk created by exposed personal and payment information.
The company also did not say when the records were exported, how long any exposure lasted or whether the data reached a third party. The 27,000-order estimate therefore remains a potential scope, not a verified victim count.
Some customers have reported fraudulent calls, Trezor said, although it did not quantify those reports or attribute specific financial losses to the breach. Trezor urged buyers to be alert for “unexpected calls, texts, emails or letters about an order.”
That warning spans calls and written communications, both of which can exploit knowledge of a customer’s purchase. The operative point is straightforward: Trezor has reported fraudulent calls, while the scale and cause remain unconfirmed.
What does a third breach in three months mean?
Trezor has disclosed the Skladon incident as its third partner data breach in three months. The sequence makes third-party data handling a recurring operational exposure for the hardware wallet maker.
It does not, by itself, establish a common attacker, a continuing campaign or a weakness in Trezor’s products. Each incident nevertheless raises the same control question: how thoroughly can vendors limit access to customer and order information, and how quickly can Trezor communicate scope?
For customers, credential reassurance does not remove personal-data risk from exposed order records. Identity fraud, payment fraud and social engineering are distinct risks, while fraudulent calls are the only misuse specifically mentioned in the disclosure. The practical distinction is narrow: Trezor says wallet credentials stayed outside the exposure, while customer records may not have.
What remains unresolved for customers?
Trezor advised buyers to remain alert for unexpected calls, texts, emails and letters concerning an order. The warning does not amount to a confirmed fraud alert for all 27,000 orders, nor does it specify reimbursement or identity-theft remediation.
Taken with the reported fraudulent calls, the warning makes unsolicited order-related contact a potential social-engineering attempt until independently verified. The company has not said whether affected customers will receive direct notices, what monitoring period applies or when remediation will finish. Until those points are settled, customers have no defined endpoint for assessing the incident’s practical reach.
When will the exposure window close?\n
A later update should clarify three measurable points, none of which the current disclosure resolves:
- The confirmed number of affected orders and records that may have been exported.
- The export dates, earliest affected records and whether third parties obtained access.
- The customer-notification process, monitoring period and status of remediation.
Trezor’s current disclosure gives no deadline for completing that work, and Skladon has not supplied a separate technical account in the report. Until Trezor or Skladon publishes a confirmed count, an export timeline and remediation status, the exposure window remains open-ended.
via tokenpost.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,576 articles