{"id":2776,"date":"2026-10-26T23:14:16","date_gmt":"2026-10-26T23:14:16","guid":{"rendered":"https:\/\/smartcryptosecurity.com\/?p=2776"},"modified":"2026-10-26T23:14:16","modified_gmt":"2026-10-26T23:14:16","slug":"major-crypto-phishing-campaign-hits-trezor-bitbox-and-cointracking-following-security-flaw-at-email-provider-brevo","status":"publish","type":"post","link":"https:\/\/smartcryptosecurity.com\/?p=2776","title":{"rendered":"Major Crypto Phishing Campaign Hits Trezor, BitBox, and CoinTracking Following Security Flaw at Email Provider Brevo"},"content":{"rendered":"<p>A critical security vulnerability in the login system of email marketing and customer relationship management platform Brevo has been exploited by an unauthorized attacker, granting unauthorized access to 138 client accounts and triggering a widespread phishing campaign across the cryptocurrency sector. The security breach allowed fraudulent emails to bypass standard authentication checks and reach roughly 347,000 subscribers of the popular hardware wallet manufacturer Trezor, alongside similar deceptive messages distributed through accounts belonging to rival hardware wallet maker BitBox and crypto portfolio tracking and tax-reporting platform CoinTracking.<\/p>\n<p>The incident came to light after affected cryptocurrency companies issued urgent warnings to their users regarding suspicious emails landing in their inboxes. Those early warnings prompted industry-wide concern over how threat actors managed to leverage trusted domain channels to distribute malicious links that appeared entirely authentic. Following the initial disclosures by the affected firms, Brevo published a detailed postmortem outlining the precise technical failure that enabled the unauthorized access, shedding light on a severe breakdown in the platform&#8217;s authentication and authorization boundaries.<\/p>\n<p>According to Brevo\u2019s official incident disclosure, the attacker initiated the breach by creating a standard account on the platform, subsequently enabling single sign-on (SSO) capabilities and inviting legitimate Brevo users into the attacker-configured environment. Under normal operating conditions and established security design principles, access granted through such an invitation should have been strictly confined to that specific organization and its immediate parameters. However, a critical authorization boundary failure occurred within the platform&#8217;s architecture, inadvertently granting the malicious actor sweeping access to every single organization and account that the invited users could legitimately reach.<\/p>\n<p>Through this systemic authorization bypass, the attacker gained unauthorized entry into 138 separate client accounts. In its postmortem analysis, Brevo detailed that six of the compromised accounts were actively weaponized to dispatch phishing emails directly to subscribers. Furthermore, contact lists were illegally exported from 43 accounts, while another 93 accounts showed no meaningful activity or data extraction during the window of compromise. The platform\u2019s public disclosure did not explicitly specify whether there was an overlap among these distinct operational categories.<\/p>\n<p>The disclosure significantly expands upon the initial warnings issued by Trezor and BitBox. By identifying Brevo as the shared third-party service provider, the security incident explains why the malicious emails successfully sailed past normal authentication mechanisms, such as Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC) checks. Because the messages originated directly from authorized email infrastructure belonging to trusted service providers, security filters and end-users alike perceived them as genuine communications.<\/p>\n<p>Cryptocurrency firms across the digital asset ecosystem have spent the days following the disclosure urgently assessing potential subscriber exposure, auditing their third-party vendor relationships, and issuing extensive remediation guidance to their communities. The incident serves as a stark reminder of the inherent supply chain risks associated with third-party software vendors, where a single vulnerability in an auxiliary business tool can instantly cascade into a major security event for high-profile enterprises handling sensitive financial audiences.<\/p>\n<h2>Crypto firms assess potential subscriber exposure<\/h2>\n<p>In an official blog post detailing the security event, Trezor confirmed that the unauthorized phishing message sent through its Brevo channel bore the alarming title &quot;Critical Security Alert: STM32 Entropy Vulnerability.&quot; The deceptive email directed recipients to click a malicious link leading to an external application designed to trick users into divulging their critical hardware wallet backups and recovery seed phrases. <\/p>\n<p>Swift action by Trezor&#8217;s internal security team mitigated the total impact of the malicious broadcast. The company successfully disabled the fraudulent destination domain at the Domain Name System (DNS) level within a mere 20 minutes of discovering the anomaly. Despite the rapid takedown, statistics provided by the company indicate that approximately 2,500 individuals accessed the malicious link before the domain was neutralized.<\/p>\n<p>A Trezor spokesperson provided further clarification regarding the scope of the distribution, noting that the initial phishing email was dispatched to roughly 347,000 customers. All impacted individuals were subsequently contacted directly by the company with urgent warnings about the risk and instructions on how to secure their accounts. Crucially, Trezor emphasized that its Brevo account stored strictly opt-in newsletter email addresses and contained no other sensitive customer data, financial records, or private keys. <\/p>\n<p>Nevertheless, out of an abundance of caution, the hardware wallet manufacturer is operating under the assumption that the worst-case scenario has occurred. Until further clarity and comprehensive logs are provided by Brevo, Trezor is treating all approximately 347,000 newsletter addresses as fully known to the attacker and potentially reusable for future phishing attempts or social engineering campaigns. Users who received the correspondence have been strongly advised to remain hyper-vigilant against subsequent fraudulent communications purporting to come from the company.<\/p>\n<p>Similar operational reviews are underway at BitBox. A spokesperson for the hardware wallet maker confirmed to industry media that an unauthorized email was sent via its Brevo integration, appearing to have reached its full mailing list consisting of newsletter subscribers and tutorial recipients. <\/p>\n<p>BitBox conducted an immediate internal audit following the breach and reported that its Brevo account held only basic subscriber email addresses and user language preferences. The company found no tangible evidence of compromised internal company credentials, unauthorized database downloads of sensitive customer records, lost user funds, or disclosed recovery phrases. However, mirroring Trezor&#8217;s conservative security stance, BitBox is treating its entire contact list as potentially accessed by the unauthorized actor while it awaits definitive, granular logs from Brevo&#8217;s engineering team to confirm the exact parameters of the data exposure.<\/p>\n<p>Meanwhile, CoinTracking took to social media to alert its user base that its Brevo account had been hijacked to distribute a fraudulent email carrying the subject line &quot;Data Breach Notice: Please refresh API Keys as soon as possible.&quot; Capitalizing on common user anxieties surrounding platform security and data leaks, the attacker attempted to coerce recipients into taking immediate, unverified action. CoinTracking urgently warned its community members not to follow any of the links embedded within the malicious correspondence and reminded users never to share their sensitive API keys or login credentials with external parties.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A critical security vulnerability in the login system of email marketing and customer relationship management&#8230;<\/p>\n","protected":false},"author":16,"featured_media":2775,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[496],"tags":[860,855,445,861,503,4,2234,385,363,433,480,896,184,1024,5,859,263],"class_list":["post-2776","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wallet-security","tag-bitbox","tag-brevo","tag-campaign","tag-cointracking","tag-cold-storage","tag-crypto","tag-email","tag-flaw","tag-following","tag-hardware","tag-hits","tag-major","tag-phishing","tag-provider","tag-security","tag-trezor","tag-wallets"],"_links":{"self":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/2776","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2776"}],"version-history":[{"count":0,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/2776\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/media\/2775"}],"wp:attachment":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2776"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2776"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2776"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}