Trezor Says ShipMonk Breach Exposed 67,000 U.S. Customers' Data It Said Was Deleted
Trezor reveals another 67,000 U.S. customers impacted in a breach at its shipping provider ShipMonk, exposing names, email addresses, phone numbers, and order numbers from 2019-2021. Trezor requested and received assurance of data deletion, but it was not removed.
Intelligence analysis by Qwen 2.5 (3B)
Trezor reports a new data breach affecting 67,000 U.S. customers, exposing personal and order information from 2019-2021. The breach was not related to Trezor's hardware wallets but occurred at its shipping provider ShipMonk.
Trezor found out that a company called ShipMonk had a problem with their data. ShipMonk was supposed to delete some information, but they didn't. Now, 67,000 people who used Trezor's wallets might have some of their personal information, like their name and email, that ShipMonk kept.
Analysis
{"heading":"The Breach at ShipMonk","subheading":"Details and Timeline","content":["Trezor disclosed that 67,000 U.S. customers were impacted in a breach at ShipMonk, a shipping provider. The exposed data includes names, email addresses, phone numbers, and order numbers from November 2019 to August 2021.","Trezor requested and received assurance from ShipMonk that the data was deleted, but it was not removed. The breach does not affect the security of Trezor's hardware wallets.","Trezor stated that the exposure is in addition to 13,689 customers previously disclosed as having had their data exposed. The breach was limited to names, cities, and email addresses (excluding shipping addresses) for 1,947 customers."]}
Key points
- Trezor reported a new data breach affecting 67,000 U.S. customers.
- The exposed data includes names, email addresses, phone numbers, and order numbers from 2019-2021.
- The breach was not related to Trezor's hardware wallets but occurred at its shipping provider ShipMonk.
The breach at ShipMonk is a reminder to always check and ensure that third-party companies are securely handling our data. This can help prevent similar issues in the future.
If ShipMonk had properly handled the data, this breach could have been avoided. This incident shows the importance of having robust security measures in place.
