Trezor Breach: What Happened at Fulfillment Partner ShipMonk

A SQL injection zero-day at fulfillment partner ShipMonk exposed order data for nearly 14,000 Trezor hardware wallet customers.

Trezor Breach: What Happened at Fulfillment Partner ShipMonk
Photo by rc.xyz NFT gallery / Unsplash

A SQL injection zero-day in a third-party analytics tool gave an attacker administrative access to Trezor's shipping and fulfillment partner, exposing order data for nearly 14,000 hardware wallet customers.

Incident Overview: Target/Organization: Trezor (via fulfillment partner ShipMonk) Initial Attack Vector: SQL injection zero-day in Metabase analytics platform Impact/Records Compromised: ~13,689 customer records (11,742 with full exposure) Timeframe: Orders placed May 10 – August 8, 2026

What Happened

Trezor, maker of popular hardware cryptocurrency wallets, disclosed that its shipping and order fulfillment partner ShipMonk suffered a data breach after an attacker exploited a critical, previously unknown SQL injection vulnerability in ShipMonk's Metabase business-intelligence deployment to gain administrative access. Trezor said its own systems and devices were not compromised — the breach was confined to ShipMonk's infrastructure.

Who's Affected

Roughly 13,689 Trezor customers who placed orders shipped between May 10 and August 8, 2026 across the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal had data exposed. Of those, 11,742 customers had full exposure — name, email, phone number, and shipping address — while the remaining 1,947 had a smaller subset (name, city, and email) leaked.

Technical Root Cause

ShipMonk traced the intrusion to a critical SQL injection zero-day in Metabase, the open-source analytics and BI platform ShipMonk uses internally. The flaw allowed the attacker to escalate to administrative access within the Metabase instance, which in turn had connections to underlying order and customer databases — a reminder that internal analytics tooling, often granted broad read access to production data for convenience, is an attractive and under-scrutinized target.

Indicators to Check For

Affected customers should be alert to phishing attempts impersonating Trezor, banks, or crypto exchanges that reference real order or shipping details — a strong signal the sender obtained data from this breach rather than guessing. Trezor has stated it will never ask for a wallet recovery seed or private keys, or ask customers to enter them anywhere online.

Remediation

ShipMonk should be patched against the disclosed Metabase SQL injection and audited for any other exposed BI or analytics tooling with database access broader than necessary. Affected Trezor customers should treat any unsolicited contact referencing their order details as suspicious, enable phishing-resistant authentication on accounts tied to the exposed email address, and never enter a wallet recovery seed into any website or application.

This is part of ColibriSec's weekly security roundup for the week of August 20, 2026.

Read more