13,689 Trezor customers affected by ShipMonk data breach

Thu, 13 Aug 2026 UTC

Trezor¹ has just disclosed² a massive data breach that affected their logistics partner ShipMonk³ on Monday (10 August 2026), which resulted in the full exposure of data for approximately 11,742 customers and partial exposure for at least 1,947 more:

[..] ShipMonk, informed us of unauthorized access to their systems containing customer data. This occurred due to a data breach. Investigation is ongoing. We’re extremely sorry to inform our community that customer personal information, including full names, phone numbers, email addresses, and shipping addresses, has been accessed by an unauthorized actor during this breach.

Incident Overview

* [Not Affected]:
 - all customers NOT contacted by help@trezor.io (check email)
* [Affected, full]: 
 - orders received within 90 days before August 8th, 2026
* [Affected, partial]:
 - TBD (may include older orders)
* [Exposed, full]:
 - name, email, phone number, shipping address for 11,742
* [Exposed, partial]:
 - name, city, email for ~1,947
* [Recommendations]:
 - watch for phishing attempts (fake emails, calls, letters, impersonation attempts)
 - never enter wallet backup on websites or share with anyone

According to the announcement, no system, product, or service was affected and Trezor devices remain entirely safe and secure.

Trezor has experienced community backlash in recent years over other issues⁴ and this latest incident - which is apparently the most serious data breach experienced by the company in the last 13 years - is bound to erode trust even more.

This is an ongoing story and the report will be updated when new information is available.

https://trezor.io ↩
https://trezor.io/blog/news/recent-customer-data-exposed-in-shipping-provider-incident ↩
https://shipmonk.com ↩
/trezor-users-exposed-unicode-domain-phishing-attack/, /trezor-under-fire-ditching-cypherpunk-ideals-swiss-finma-aml-requirements-aopp/ ↩

BTCPay Server discloses 'critical' vulnerability which may result in loss of funds

Fri, 07 Aug 2026 UTC

BTCPay Server¹ has just released a security advisory² detailing a critical vulnerability that is being actively exploited which may result in the loss of funds, urging operators to update or turn off servers immediately:

Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.

Advisory

a) Update from 2.4.1 to 2.4.2 or b) turn off servers until update is possbile
(after update) Completely refresh macaroons and macaroons.db
(after update) Completely refresh auth strings for other LN backends
for hot on-chain BTCPay wallets: move funds and recreate the wallet

It is worth mentioning that Bitcoin Red Team³ reported and helped address the vulnerability.

More details about this incident can be found in PR #7498⁴.

Note that patching does NOT undo earlier compromise: credentials for instances that were reachable while unpatched must be treated as exposed.

This is an ongoing story and the report will be updated when new information is available.

Update: more details about ongoing incident available⁵.

https://btcpayserver.org/ ↩
https://farside.link/nitter/BtcpayServer/status/2085755643659522240 ↩
https://opensats.org/funds/red, https://farside.link/nitter/craigraw, https://farside.link/nitter/callebtc/status/2085755935352328470 ↩
https://github.com/btcpayserver/btcpayserver/pull/7498 ↩
https://farside.link/nitter/i/article/2085865561137831938 ↩

Monero Observer

13,689 Trezor customers affected by ShipMonk data breach

Incident Overview

BTCPay Server discloses 'critical' vulnerability which may result in loss of funds

Advisory