Skip to main content
Mallory
← Back to News
third-party-vendor-breachbreach-disclosure-notificationcryptocurrency-platform-riskmass-credential-exposure

ShipMonk Breach Exposes Trezor Customer Contact and Shipping Data

Breach & Incident Intelligence · 13 sources · Updated 2mo ago · First seen Aug 13, 2026

ShipMonk Breach Exposes Trezor Customer Contact and Shipping Data

Trezor disclosed that unauthorized access at third-party logistics provider ShipMonk exposed customer order data for 13,689 hardware wallet buyers, affecting recent deliveries across the U.S., U.K., Sweden, Colombia, Brazil, Italy, and Portugal. The exposed information included full names, email addresses, phone numbers, and shipping addresses for 11,742 customers, while 1,947 others had more limited data exposed, such as name, city, and email address. Trezor said ShipMonk notified it of the incident after attackers accessed systems containing order records tied to shipments delivered between May 10 and Aug. 8, 2026.

Trezor said its own infrastructure, wallets, devices, and firmware were not compromised, but warned affected customers to expect phishing, impersonation, and possible physical-security risks because the leaked data links identities to hardware wallet purchases. The company said its 90-day data retention policy limited the scope because older records had already been deleted or anonymized, and it has notified impacted users by email while working with ShipMonk as the provider secures and hardens affected systems. Trezor also said it plans to roll out an Anonymous Delivery option, first in the EU and later in the U.S., to reduce future customer exposure.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

10 events · May 10, 2026 – Sep 2, 2026
  1. Sep 2, 20263mo ago

    ShipMonk identifies 67,000 additional Trezor customers in historical data exposure

    ShipMonk notified Trezor that historical order data from November 2019 through August 2021 had also been exposed, affecting approximately 67,000 additional U.S. customers. The files included names, email addresses, phone numbers, shipping addresses, and order numbers, raising the incident's total impact to more than 80,000 Trezor customers.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers
  2. Reported Aug 14, 20263mo ago

    Trezor expands exposed customer count and says some earlier orders may be affected

    Trezor said 11,742 customers had names, email addresses, phone numbers, and shipping addresses exposed, and an additional 1,947 customers had names, home cities, and email addresses exposed. It also said some of the additional group may have placed orders before 2026-05-10, indicating the exposure may extend beyond the previously identified shipment window.

    Crypto wallet maker Trezor confirms 13,000 customers' details exposed in logistics breach
  3. Reported Aug 14, 20263mo ago

    ShinyHunters claims Metabase attack and leaks alleged stolen data

    SecurityWeek reported that the extortion group ShinyHunters claimed responsibility for an attack on Metabase and leaked data allegedly stolen from Metabase on Wednesday. This introduced a new attribution-related development connected to the ShipMonk/Trezor exposure, though responsibility for the ShipMonk breach itself remained unconfirmed.

    14,000 Trezor Customers Impacted by Data Breach at ShipMonk - SecurityWeek
  4. Reported Aug 13, 20263mo ago

    Trezor announces Anonymous Delivery plan

    Trezor announced plans for an Anonymous Delivery option intended to reduce future exposure of customer shipping data. The planned feature includes dedicated checkout, locker pickup, neutral packaging, generic sender details, and deletion of shipping identifiers after delivery.

    Trezor ShipMonk Data Breach Exposes Personal Data of Over 13,000 Hardware Wallet Customers
  5. Reported Aug 13, 20263mo ago

    ShipMonk secures affected systems as investigation continues

    Trezor said ShipMonk had secured and hardened the affected systems after the breach. Trezor also said it was working with ShipMonk to investigate what happened and determine exactly which data was accessed.

    Trezor ShipMonk Data Breach Exposes Personal Data of Over 13,000 Hardware Wallet Customers
  6. Reported Aug 13, 20263mo ago

    Trezor emails affected customers and warns of phishing risk

    Trezor said it notified affected customers by email from help@trezor.io and warned them to expect phishing, spoofed calls, fraudulent letters, and impersonation attempts. The company said customers who did not receive the notification email were not part of the exposed set.

    Trezor ShipMonk Data Breach Exposes Personal Data of Over 13,000 Hardware Wallet Customers
  7. Reported Aug 13, 20263mo ago

    Trezor discloses ShipMonk breach affecting 13,689 customers

    Trezor disclosed that unauthorized access at third-party logistics provider ShipMonk exposed fulfillment-related customer data for about 13,689 customers. Trezor said its own infrastructure, wallets, devices, and firmware were not compromised.

    Trezor ShipMonk Data Breach Exposes Personal Data of Over 13,000 Hardware Wallet Customers
  8. Aug 10, 20263mo ago

    ShipMonk notifies Trezor of unauthorized access

    On 2026-08-10, ShipMonk informed Trezor that unauthorized access had occurred in systems containing customer data. The affected systems held order-fulfillment information for Trezor customers.

    Trezor Shipping-Provider Breach Exposes Data of 13,689 Customers | The Defiant
  9. Aug 6, 20263mo ago

    ShipMonk links Trezor data exposure to Metabase vulnerability

    ShipMonk told affected customers that attackers exploited a vulnerability in the third-party analytics platform Metabase to access data tied to ShipMonk and its customers. ShipMonk said Metabase notified it on 2026-08-06, and that Metabase patched the flaw and invalidated active sessions.

    Trezor discloses data breach affecting nearly 14,000 customers
  10. May 10, 20266mo ago

    Trezor customer orders shipped during exposed data window

    The customer records later exposed in the ShipMonk incident were tied to orders delivered between 2026-05-10 and 2026-08-08. Trezor said the affected population consisted of recent shipments within that period.

    Trezor ShipMonk Data Breach Exposes Personal Data of Over 13,000 Hardware Wallet Customers
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Organizations

2 linked
TrezorShipMonk

Breaches

2 linked
SHIPMONK-2026-08TREZOR-2026-08

Observables

1 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.