Summary
- Brevo's postmortem traced the Trezor phishing attack to an SSO authorization flaw.
- The flaw let one attacker access 138 Brevo customer accounts across tenants.
- 347,000 Trezor newsletter addresses received the fake security alert.
- Six hijacked accounts sent phishing; 43 had contact lists exported.
- Trezor is treating all newsletter addresses as known to the attacker.
The Brevo SSO flaw behind the Trezor phishing attack has a postmortem now, and it is worse than a stolen password: a single sign-on authorization boundary failure let one attacker account reach into 138 legitimate Brevo customer organizations. The mechanics, published by Brevo on September 10, are almost elegant in their abuse of normal product behavior. The attacker created a Brevo account, enabled SSO, and invited real Brevo users into the attacker-controlled organization. Due to a permission boundary failure across multi-tenant accounts, joining the attacker's SSO organization granted access to every legitimate corporate account those invited users could reach. From there the attacker hijacked the email infrastructure of Trezor, BitBox, and crypto tax tool CoinTracking, and sent phishing mail from authenticated corporate channels that passed SPF and DKIM by design, because it genuinely came from Brevo's infrastructure.
The numbers quantify the blast radius. Of the 138 accessed accounts, six were used to dispatch phishing emails and 43 had contact lists exported. Trezor's fake "Critical Security Alert: STM32 Entropy Vulnerability" email, which weaponized panic from the real Coldcard entropy breach, went to all 347,000 opt-in newsletter addresses. About 2,500 users opened the link; the malicious domain was taken down at the DNS level within 20 minutes. Trezor confirmed no hardware, recovery seed, or internal system was compromised, and a spokesperson put the residual risk plainly: "Until we hear more from Brevo, we are treating all roughly 347,000 newsletter addresses as known to the attacker and possibly reusable for phishing."
What the Brevo SSO Flaw Teaches About Multi-Tenant Trust
This incident closes the loop on a story that broke across the industry in early September: the vendor was Brevo, the breach was architectural, and the consequences were three brands' customers receiving mail that no email filter could catch. The lesson is not about Trezor's firmware, which held, or about SPF and DKIM, which worked exactly as specified and still failed. It is that multi-tenant SaaS concentrates trust, and one permission-boundary bug in an SSO invite flow converts a marketing tool into a cross-tenant phishing launcher. Any company whose security model relies on "the email came from our provider's IPs" inherited that risk this week, the same class of authenticity problem behind Binance-branded smishing campaigns. For the individuals in the exported lists, the exposure now compounds with the earlier ShipMonk logistics breach, which exposed roughly 80,689 Trezor customer records including shipping addresses, the targeting stack that makes both digital and physical seed-phrase coercion attacks feasible.
Why Newsletter Lists Are the Real Crown Jewels
The uncomfortable industry takeaway: hardware wallet makers spend heavily on secure elements while their subscriber databases circulate. A 347,000-address list of self-identified hardware wallet owners, verifiably interested in security alerts, is the highest-value phishing target list in consumer crypto, and it has now been exported once and treated as burned. Users who opened the fake alert and typed seed phrases anywhere should assume loss and move remaining funds immediately; everyone else should apply the standing rule that security alerts are verified on the vendor's official channel, never via emailed links, the same discipline that separates the genuine firmware disasters from the ones that only exist in your inbox.
Watch for a second campaign against the 43 exported lists. Brevo patched the flaw and published the postmortem, but the data does not un-leak. The wallets were never the weak point. The mailing list was.













































