Skip to content
ShipMonk Data Breach Affects 67,000 Trezor Customers

ShipMonk Data Breach Affects 67,000 Trezor Customers

First seen 4 Sep 2026, 14:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •September 5, 2026 at 13:48 UTC
  • •67,000 additional Trezor customers affected by ShipMonk data breach.
  • •Older order records that should have been deleted were leaked.
  • •Breach significantly expands the scope of an earlier reported incident.

Trezor has confirmed that a data breach involving its fulfillment provider, ShipMonk, has exposed personal and order information of approximately 67,000 additional U.S. customers. This breach significantly expands the scope of an incident initially reported in August 2026. The exposed data includes older U.S. order records that should have been deleted but remained in the leaked dataset. The breach relates to Trezor orders processed during a partnership with ShipMonk that lasted from November 2019 to 2021. As of September 4, 2026, Trezor has acknowledged the breach and is working to inform affected customers. The incident raises concerns about data retention practices and the handling of sensitive customer information by third-party vendors.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 49d ago How this analysis works

Timeline

2026-08-01
Initial data breach reported
Trezor first reported a data breach involving ShipMonk, affecting an unspecified number of customers.
Gbhackers
2026-09-02
Trezor informed of expanded breach
Trezor was notified that the breach included additional data from older U.S. orders.
Cybersecuritynews
2026-09-04
Trezor confirms breach details
Trezor publicly confirmed the breach affecting 67,000 additional customers and the nature of the leaked data.
Gbhackers

More articles in this cluster (12)

Following this threat?

Track ShipMonk in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed