Loading prices…
🩸BEARISH

ShipMonk breach exposes data of 67,000 more Trezor customers

The incident highlights the privacy risk of third-party fulfillment, while Trezor says its own systems and users' devices remain secure.

ShipMonk breach exposes data of 67,000 more Trezor customers
ShipMonk breach exposes data of 67,000 more Trezor customers

Trezor said a data breach at its shipping provider, ShipMonk, now affects another 67,000 U.S. customers who placed orders between November 2019 and August 2021. Exposed records included names, email addresses, phone numbers, shipping addresses and order numbers.

Why it matters

The incident makes third-party data retention the central privacy issue. Trezor said ShipMonk had repeatedly confirmed the data was deleted, but it remained in the provider's systems.

Market impact

The exposure concerns customer and delivery records, not wallet-device security. Trezor said its own systems were not compromised and users' devices remain secure, leaving privacy controls at fulfillment partners as the key issue for hardware-wallet customers.

Frequently asked questions

  1. Which orders were included in the expanded ShipMonk breach?

    Orders placed by U.S. customers between November 2019 and August 2021 were included in the affected group.

  2. What customer information did the breach expose?

    The records included names, email addresses, phone numbers, shipping addresses and order numbers.

  3. What happened after ShipMonk confirmed the data was deleted?

    Trezor said the data remained in ShipMonk's systems despite the provider's repeated deletion confirmations.

  4. Were Trezor's systems or users' devices compromised?

    No. Trezor said its own systems were not compromised and users' devices remain secure.

  5. What broader privacy issue does the incident raise for hardware-wallet users?

    It makes third-party data retention a central privacy issue because customer and delivery records remained in ShipMonk's systems.

Source attribution
Aggregated from WuBlockchain · Verified · Last refreshed 57m ago
Open original →