Case period: Provider notified Trezor on 2026-08-10. This article is a retrospective review.
The notice changed over time
Trezor's 13 August 2026 notice described a customer-data incident at shipping provider ShipMonk, which had notified Trezor on 10 August. A 4 September update widened the stated scope to include an additional set of older US orders. Readers assessing their exposure should therefore use the updated notice rather than only the first announcement.
Why order information matters
The reported exposure involved customer and order information, with different fields present in different records. It was not described as a disclosure of wallet recovery phrases. Names, addresses and purchase context can nevertheless make fraudulent calls, parcels or messages appear unusually credible.
How to handle a convincing follow-up
Knowing what device you bought is not proof that a caller represents the manufacturer. Verify support independently before following instructions, especially requests to replace a device, restore a wallet or reveal a backup. Keep the physical message or shipping label as evidence where relevant. Record which notice version you consulted and which order it concerns. This case illustrates why a breach update can materially change the affected population; Wallet Beep is not claiming to have checked individual customer records.
Source and review date
Trezor — original source. Source published: 2026-08-13. Source updated: 2026-09-04. Source checked: 2026-10-23.
This is an original Wallet Beep editorial summary. Consult the linked source for its full context and any later updates.