レポート一覧に戻る
Security
Incident
Wallet
Privacy
Data Minimization
2026年08月13日

What Broke Was the Purchase Record, Not the Device: The Threat Model of Self-Custody Has Moved

破られたのは端末ではなく購買記録 ── セルフカストディの脅威モデルが移動している

What Broke Was the Purchase Record, Not the Device

On August 13, 2026, Trezor disclosed that an unauthorized party had obtained customer order data through a breach at ShipMonk, one of its shipping providers. The company was notified on August 10.

The exposed data comprises the information required for delivery: full names, shipping addresses, phone numbers and email addresses. Full exposure affected 11,742 customers, while partial exposure limited to name, city and email address affected 1,947, for a total of approximately 13,689 people. The affected orders were shipped between May 10 and August 8, 2026 to the United States, United Kingdom, Sweden, Colombia, Brazil, Italy and Portugal. Japan was not among them.

Trezor states clearly that its own systems were not compromised and that hardware wallets, private keys and wallet backups were unaffected. That is almost certainly accurate. Yet the company also acknowledges that this is the first time since its founding in 2013 that customer phone numbers and shipping addresses have been exposed, and it describes the seriousness in unusually direct terms.

The cryptographic boundary held. What broke was the boundary around information about who is using that cryptography and where they live.

A Ninety-Day Retention Policy Determined the Scale of the Damage

The second point worth noting is that the size of the exposure was determined not by cryptography or security products but by a data retention policy.

Trezor deletes or anonymizes purchase data from its own store ninety days after delivery, and it contractually imposed the same condition on its fulfillment partners. By the company's explanation, ninety days was chosen as the shortest window that still covers the full life of an order, including delivery, returns, refunds and replacements. As a result, orders older than ninety days no longer existed in ShipMonk's systems, and exposure was capped at roughly 13,689 people.

For comparison, the incident Ledger experienced in 2020 exposed personal information for around 270,000 people through an e-commerce platform. On January 5, 2026, Ledger disclosed a further incident in which customer names, addresses, email addresses and phone numbers were accessed through Global-e, its cross-border e-commerce and payment platform. There too, neither Ledger's own systems nor its hardware were compromised.

The same structural failure keeps recurring through different vendors. What separated the outcomes was not spending on security but design choices about how little data to hold. Data minimization is, before it is a compliance requirement, an engineering parameter that sets the ceiling on damage.

In 2026, Self-Custody Is Failing at Three Layers

Placing this year's incidents side by side shows that self-custody is failing in places other than where the industry has been looking.

The first layer is the supply chain of key generation. In the Coldcard incident that began on July 30, a build configuration error introduced in a March 2021 firmware release caused seed generation to fall back on a software pseudorandom number generator rather than the device's hardware random number generator. Effective key strength reportedly collapsed from a designed 128 bits to as little as 40 bits on older devices. According to Galaxy Research, 1,082.65 BTC, worth roughly 70.2 million US dollars at the time (about 11.2 billion yen at 160 yen to the dollar), was swept from 1,196 addresses in 41 minutes on July 30 alone. Cumulative movement is put at roughly 1,816 BTC, about 116 million dollars (roughly 18.6 billion yen), across more than 5,200 addresses, with estimates varying by source. DeFiLlama's tally attributes about 46 percent of July's total 247.4 million dollars in crypto theft to this single incident. The devices were offline. The assets left anyway.

The second layer is the supply chain of purchase records. This is where the Trezor and Ledger incidents sit. What leaks here is not the asset but the real name and location of someone likely to hold one.

The third layer is physical attack using that information. Chainalysis recorded 46 violent crypto-related incidents globally through late June 2026, against 40 at the same point in 2025. CertiK estimates losses from physical coercion at 124 million dollars (roughly 19.8 billion yen) in the first half of 2026.

What stands out is the falling success rate. Chainalysis reports that only 12 of 46 incidents, or 26 percent, resulted in a transfer of funds in 2026, down from 49 percent (47 of 95) in 2025 and 67 percent (32 of 48) in 2024. The firm attributes the decline substantially to France, where a compromise of tax agency records expanded the targetable victim population considerably, making attacks more numerous and more indiscriminate and therefore less often successful than the intelligence-driven attacks of prior years.

Put differently, a leaked address list does not only make attacks more precise. It also induces cruder, more numerous attacks. The falling success rate is not an improvement in conditions but the reverse side of a widening base of victims.

From "Who Holds the Key" to "Who Knows You Hold It"

The self-custody debate has long turned on a single question: who holds the key. Leave assets with an exchange and you bear the risk of its failure or misconduct; hold them yourself and you avoid that.

The operative threat in 2026 sits outside that framing. The act of purchasing a hardware wallet functions as a signal that the buyer probably holds meaningful assets. A dataset joining that signal to a real name, street address and phone number is an unusually high-quality target list for an attacker. And that dataset is held not by the wallet vendor itself but by payment processors and fulfillment partners, firms that sit outside the crypto industry altogether.

Trezor's stated response is instructive. Alongside recommending anonymous email addresses, payment in crypto and the use of a P.O. box, the company said it aims to offer an anonymous delivery option combining a dedicated checkout, locker pickup, neutral packaging, generic sender details and automatic deletion of shipping identifiers after delivery, targeting the European Union in September 2026 and the United States by the end of the year.

This is not merely remediation but an attempt to build privacy protection into the product specification. Shipping physical goods worldwide makes it impossible to eliminate data sharing entirely. Given that, the only remaining levers are the quantity of information shared and the length of time it is held. The axis of competition is shifting to exactly there.

Business Development Insights

  1. Treat data retention periods as a parameter that caps damage, not as a compliance line item. What limited this exposure to roughly 13,689 people was neither cryptography nor a security product but a policy of deleting or anonymizing data ninety days after delivery, contractually extended to fulfillment partners. In any business handling customer data, shortening retention is among the highest-return risk reduction measures available. It is worth auditing, from a risk management rather than legal perspective, whether your retention period is set to the genuine minimum operational window and whether that condition actually binds your vendors.
  2. Extend vendor inventories beyond system integrations to logistics and payment processing. Both customer data exposures this year originated not with the wallet vendors but with a shipping provider and a cross-border e-commerce and payment platform. However strong an organization's own security posture, information must be handed outside to deliver an order, so the attack surface scales with the number of vendors. For financial institutions and corporates handling digital-asset-related physical goods, or any service involving delivery to customers, the practical starting point is to enumerate what data each vendor holds and for how long, and to confirm that deletion obligations are written into the contract.
  3. Change the incident response triage criteria for personal data of likely crypto holders. Ordinary personal data breaches are assessed against risks of impersonation and financial fraud, but exposure of the address and phone number of a customer presumed to hold crypto assets translates directly into risk of physical harm. Losses from physical coercion in the first half of 2026 are estimated at around 124 million dollars, with home invasions rising as a share of incidents. In Japan as well, hardware wallets are now being distributed in connection with corporate service offerings, meaning the names and business addresses of corporate treasury staff could appear on comparable lists. Breach notifications should include warnings about physical security, not only phishing, and the criteria for making that call should be settled in peacetime.

Sources

Supervisor

Akihisa Ishida

Cabinet Inc. Founder CEO

Since 2017, He has been consistently engaged in token and NFT utilization, blockchain game planning and development, and NFT-based business development. Having contributed to over 80 blockchain products—including projects for major entertainment companies listed in Tokyo Stock Exchange —He has served in various key roles such as Business Lead, Designer, PM, and Advisor. In 2021, founded Cabinet Inc.

Disclaimer

This report has been prepared solely for informational purposes regarding crypto assets and related markets, and is not intended to recommend, solicit, or offer the purchase, sale, holding, or any other transaction of any specific crypto asset. It does not constitute investment advice, investment solicitation, or the sale or intermediation of financial products as defined under the Financial Instruments and Exchange Act or any other applicable laws and regulations, nor does it constitute tax, legal, or accounting advice.

The information contained in this report is based on sources believed to be reliable at the time of preparation; however, we make no representation or warranty, express or implied, as to its accuracy, completeness, timeliness, or usefulness. Crypto assets are subject to significant price volatility and may result in the loss of principal or other financial losses. Any investment decision shall be made solely at the user's own discretion and responsibility, and we accept no liability whatsoever for any damages arising out of or in connection with the use of this report.

Blockchain Business Consultation

From idea-stage brainstorming and technical validation (PoC) to implementation and operations, Cabinet provides end-to-end business development consulting. Start with a free consultation today.

Sign Up for Newsletter

Beyond the content of this report, we will deliver the latest industry information and exclusive reports by email.