Skip to main content
Mallory
← Back to News
third-party-vendor-breachmass-credential-exposureactively-exploited-vulnerabilitybreach-disclosure-notification

ShipMonk Metabase Flaw Exposes Data of 67,000 Trezor Customers

Active Exploitation · 12 sources · Updated 2mo ago · First seen Sep 4, 2026

ShipMonk Metabase Flaw Exposes Data of 67,000 Trezor Customers

Trezor confirmed that a breach at fulfillment provider ShipMonk exposed historical order and personal data for roughly 67,000 additional U.S. customers, bringing the total affected population to more than 80,000. The records relate to orders placed from November 2019 through August 2021 and include names, email addresses, phone numbers, shipping addresses, and order numbers. Trezor said its own systems, hardware wallets, wallet backups, and parcel-content details were not compromised.

Attackers reportedly gained access by exploiting CVE-2026-72898, a critical SQL-injection zero-day in the Metabase analytics platform that could enable administrator-level access. Halborn attributed the incident to the ShinyHunters extortion group. Trezor said ShipMonk retained data that it had represented as deleted or anonymized, and warned impacted customers to expect phishing, impersonation, fraudulent calls or letters, and heightened physical-security risks tied to hardware-wallet ownership.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

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

13 events · Aug 6, 2026 – Sep 4, 2026
  1. Reported Sep 8, 20262mo ago

    Trezor customers report phishing calls and QR-code letters

    Following the ShipMonk data exposure, Trezor customers reported receiving phishing telephone calls and physical letters containing QR codes. The reported scams use the exposed customer contact and delivery information for targeting.

    Trezor customers hit with phishing calls and letters after shipping-partner breach - Help Net Security
  2. Reported Sep 7, 20262mo ago

    Trezor says its systems and hardware wallets were not compromised

    Trezor stated that the ShipMonk breach did not compromise Trezor's own systems, operations, services, or hardware-wallet devices. It warned affected customers that exposed contact and address data could still facilitate phishing, fraud, and physical-security risks.

    Trezor data breach impact now reaches 81,000 customers
  3. Reported Sep 5, 20262mo ago

    Halborn attributes ShipMonk breach to ShinyHunters

    Halborn assessed that the ShinyHunters extortion gang was responsible for the ShipMonk breach, describing it as a supply-chain attack that used the Metabase flaw to compromise customers, steal data, and extort the organization.

    Trezor Says ShipMonk Breach Exposed 67,000 U.S. Customers' Data It Said Was Deleted
  4. Reported Sep 4, 20262mo ago

    Reporting identifies critical Metabase zero-day as intrusion vector

    Subsequent reporting characterized the incident as exploitation of CVE-2026-72898, a critical CVSS 10.0 SQL-injection zero-day in Metabase that could provide administrator access to affected instances.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  5. Sep 4, 20263mo ago

    Trezor considers legal action and accelerates anonymous delivery options

    Trezor said it was evaluating potential legal action against ShipMonk and accelerating development of anonymous delivery options to reduce the personal data transferred from its systems. It also said ShipMonk had secured and hardened the affected systems following the incident.

    Trezor Supply Chain Breach Now Impacts 81,000 Customers - Infosecurity Magazine
  6. Sep 4, 20263mo ago

    Trezor says ShipMonk retained data it had assured was deleted

    Trezor stated that it had repeatedly received written assurances that the historical customer data had been deleted or anonymized under its retention policy, but the affected records remained in ShipMonk systems.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  7. Sep 4, 20263mo ago

    Trezor reveals exposure of 67,000 additional U.S. customers

    Trezor confirmed that ShipMonk's breach also exposed historical order records for about 67,000 additional U.S. customers, involving orders from November 2019 through August 2021. The records included names, emails, phone numbers, shipping addresses, and order numbers, bringing the total affected population above 80,000.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  8. Sep 3, 20263mo ago

    Shipup confirms Metabase-linked breach affecting e-commerce brands

    Shipup publicly confirmed a data breach caused by exploitation of a critical Metabase Cloud vulnerability. The incident exposed customer names, email addresses, and, where provided, phone numbers for customers of Micromania, Easypara, Aroma-Zone, Le Printemps, and Citadium; Shipup did not disclose the number affected.

    Fuite de données Shipup : Le Printemps, Citadium et Aroma Zone victimes via Metabase | CyberVeille
  9. Aug 14, 20263mo ago

    Trezor says some partially exposed records involve older orders

    Trezor updated its disclosure to acknowledge that some records initially characterized as partially exposed were associated with older orders.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  10. Aug 13, 20263mo ago

    Trezor initially discloses ShipMonk customer-data exposure

    Trezor disclosed that 11,742 customers had names, email addresses, phone numbers, and shipping addresses exposed, while 1,947 others had partial exposure of names, cities, and email addresses. The initially identified records related to orders placed from May 10 through August 8, 2026, across seven countries.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  11. Aug 10, 20263mo ago

    ShipMonk notifies Trezor of unauthorized system access

    ShipMonk informed Trezor that its systems had experienced unauthorized access, initiating Trezor's response to the logistics-provider incident.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
  12. Aug 6, 20263mo ago

    Metabase issues advisory and mitigation guidance for critical SQL injection flaw

    Metabase published a security advisory for the critical unauthenticated SQL-injection vulnerability, which can grant administrator privileges on vulnerable instances. CERT-FR reported numerous compromises and urged immediate patching, while documenting request patterns and containment actions for potentially exposed deployments.

    Vulnérabilité dans Metabase - CERT-FR
  13. Aug 6, 20263mo ago

    Metabase alerts ShipMonk to unauthorized data access

    Metabase notified ShipMonk that an unauthorized party had used a software flaw to access account and customer data.

    Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers | Cryptika Cybersecurity
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Threat actors

1 linked

Organizations

3 linked
SatoshilabsTrezorShipMonk

Breaches

4 linked
SHIPMONK-2026-08TREZOR-2026-08TREZOR-2026-09SATOSHILABS-2026-08
Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
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.