Threat reportPhishingTL-2026-2432
Trezor Warns of Phishing Attacks After Third-Party Email Provider Breach ("STM32 Entropy Vulnerability" Lure)
Trezor's third-party email provider was breached, letting attackers send a phishing email from the legitimate help@trezor.io address claiming a fake STM32 microcontroller entropy flaw exposed seed phrases to brute-forcing. The email passed SPF/DKIM/DMARC checks; BitBox reported a near-identical campaign the same day, pointing to a shared compromised marketing/email provider.
Key facts
| Identifiers | TL-2026-2432 |
|---|---|
| Also known as | STM32 Entropy Vulnerability Phishing Campaign |
| Severity | MEDIUM |
| Affected products | SatoshiLabs (Trezor) Trezor customer email communications sent via third-party email provider (help@trezor.io); BitBox (Shift Crypto) BitBox customer newsletter/email communications |
| MITRE ATT&CK techniques | T1078.004 Valid Accounts: Cloud Accounts, T1199 Trusted Relationship, T1204.001 User Execution: Malicious Link, T1566.002 Phishing: Spearphishing Link, T1583.001 Acquire Infrastructure: Domains, T1584.006 Compromise Infrastructure: Web Services, T1586.002 Compromise Accounts: Email Accounts, T1589.002 Gather Victim Identity Information: Email Addresses, T1657 Financial Theft, T1684.001 Impersonation |
| Motivation | FINANCIAL |
| Target sectors | cryptocurrency, finance |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 10 cited sources |
Detection coverage
As of 2026-09-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2432 across Splunk SPL, Microsoft KQL and Sigma, covering 11 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Trusted-Domain Phishing — 'STM32 Entropy Vulnerability' Vendor-Impersonation Lure (Auth-Passing)
Detects inbound mail matching the 'Critical Security Alert: STM32 Entropy Vulnerability' lure theme (or close variants) that fully passes SPF/DKIM/DMARC because it originated from the legitimate vendor domain via a breached third-party ESP (T1199 Trusted Relationship abuse, T1656 Impersonation, T1566.002 Spearphishing Link). Authentication-passing phishing bypasses classic spoofed-domain heuristics, so this rule keys on lure content/subject and burst-send volume from a normally low-volume sender rather than authentication failure.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1566.002, T1656, T1199, T1589.002
- Data sources: ms_defender_office365_emailevents, proofpoint_message_logs, mimecast_siem_logs, o365_management_activity
- Severity: high
- Confidence: high
Splunk SPL
index=email (sourcetype="ms:o365:reporting:messagetrace" OR sourcetype="proofpoint:message:json" OR sourcetype="mimecast:siem")
| eval spf_result=coalesce(spf, spf_result, "unknown"), dkim_result=coalesce(dkim, dkim_result, "unknown"), dmarc_result=coalesce(dmarc, dmarc_result, "unknown")
| where spf_result="pass" AND dkim_result="pass" AND dmarc_result="pass"
| where match(lower(subject), "critical security alert") OR match(lower(subject), "stm32") OR match(lower(subject), "entropy vulnerability") OR (match(lower(subject), "security alert") AND match(lower(body_preview), "seed phrase|recovery phrase|wallet"))
| eval sender_domain=lower(mvindex(split(sender_address, "@"), 1))
| stats count as recipient_count, min(_time) as first_seen, max(_time) as last_seen, dc(recipient_address) as unique_recipients, values(subject) as subjects by sender_address, sender_domain
| lookup sender_baseline_avg_daily_volume sender_address OUTPUT avg_daily_volume
| eval baseline=coalesce(avg_daily_volume, 50)
| where recipient_count > (baseline * 5)
| table first_seen last_seen sender_address sender_domain recipient_count unique_recipients baseline subjects
| sort -recipient_countMicrosoft KQL
EmailEvents
| where Timestamp > ago(24h)
| where AuthenticationDetails has "spf=pass" and AuthenticationDetails has "dkim=pass" and AuthenticationDetails has "dmarc=pass"
| where Subject has_any ("Critical Security Alert", "STM32", "Entropy Vulnerability") or (Subject has "Security Alert" and (Subject has "seed" or Subject has "wallet" or Subject has "recovery phrase"))
| extend SenderDomain = tostring(split(SenderFromAddress, "@")[1])
| summarize RecipientCount = dcount(RecipientEmailAddress), FirstSeen = min(Timestamp), LastSeen = max(Timestamp), Subjects = make_set(Subject) by SenderFromAddress, SenderDomain
| join kind=leftouter (
EmailEvents
| where Timestamp between (ago(30d) .. ago(1d))
| summarize DailyAvg = count() / 29.0 by SenderFromAddress
) on SenderFromAddress
| extend Baseline = coalesce(DailyAvg, 50.0)
| where RecipientCount > (Baseline * 5)
| project FirstSeen, LastSeen, SenderFromAddress, SenderDomain, RecipientCount, Baseline, Subjects
| order by RecipientCount descSigma
title: Authentication-Passing Vendor-Impersonation Phishing Burst (STM32 Entropy Lure Pattern)
id: 7a1e6c2e-4f3d-4b8a-9e6f-2c1a5d7b9e01
status: experimental
description: Detects an abnormal burst of authenticated (SPF/DKIM/DMARC pass) outbound-looking mail from a legitimate vendor domain carrying a fabricated critical-vulnerability lure theme, consistent with a breached third-party ESP being abused to send mail as the real domain (Trezor/BitBox 'STM32 Entropy Vulnerability' campaign, Sept 2026).
references:
- https://www.bleepingcomputer.com/news/security/trezor-warns-users-of-email-provider-breach-phishing-attacks/
- https://cointelegraph.com/news/trezor-bitbox-hardware-wallet-phishing-emails
author: Threadlinqs Team
date: 2026-09-10
tags:
- attack.reconnaissance
- attack.t1589.002
- attack.initial-access
- attack.t1566.002
- attack.t1199
- attack.defense-evasion
- attack.t1656
- detection.email-phishing
logsource:
category: application
product: m365
service: email
detection:
auth_pass:
AuthenticationDetails|contains|all:
- 'spf=pass'
- 'dkim=pass'
- 'dmarc=pass'
lure_subject:
Subject|contains:
- 'Critical Security Alert'
- 'STM32'
- 'Entropy Vulnerability'
- 'seed phrase'
- 'recovery phrase'
condition: auth_pass and lure_subject
falsepositives:
- Genuine vendor security advisory emails referencing a real disclosed CVE — verify against the vendor's official blog/app before dismissing as false positive
- Internal security-awareness phishing simulation using a similar lure theme
level: highKnown false positives:
- Legitimate vendor security advisory that genuinely discloses a real hardware/firmware vulnerability, sent through the same ESP at similarly high volume
- Internal red-team/awareness phishing simulation using a similarly themed lure and the real corporate domain
Tuning notes: Maintain a per-sender 30-day rolling baseline (sender_baseline_avg_daily_volume) to avoid alerting on legitimate scheduled newsletters; tighten the lure keyword list per confirmed campaign IOCs as new subject-line variants surface; exclude verified internal phishing-simulation platforms (KnowBe4, Proofpoint Security Awareness) by sender header.
- Trusted-Domain Phishing — 'STM32 Entropy Vulnerability' Vendor-Impersonation Lure (Auth-Passing) · unlock with TL Creds
- Compromised Email/Marketing-Platform Account — ESP Takeover Enabling Send-As-Legit-Domain Abuse · unlock with TL Creds
- Click-Through to Phishing Landing Page + Wallet-Drain Precursor (Seed-Phrase Harvesting Page) · unlock with TL Creds
- Trusted-Domain Phishing — 'STM32 Entropy Vulnerability' Vendor-Impersonation Lure (Auth-Passing) · unlock with TL Creds
- Compromised Email/Marketing-Platform Account — ESP Takeover Enabling Send-As-Legit-Domain Abuse · unlock with TL Creds
- Click-Through to Phishing Landing Page + Wallet-Drain Precursor (Seed-Phrase Harvesting Page) · unlock with TL Creds
- Compromised Email/Marketing-Platform Account — ESP Takeover Enabling Send-As-Legit-Domain Abuse · unlock with TL Creds
- Click-Through to Phishing Landing Page + Wallet-Drain Precursor (Seed-Phrase Harvesting Page) · unlock with TL Creds
Indicators of compromise
As of 2026-09-10, Threadlinqs Intelligence tracks 11 indicators of compromise for TL-2026-2432.
Technical analysis
On September 10, 2026, hardware wallet manufacturer Trezor (operated by SatoshiLabs) warned customers that a third-party email provider it uses had been breached, and the access was abused to send a phishing email from Trezor's legitimate help@trezor.io address. The message, titled "Critical Security Alert: STM32 Entropy Vulnerability," falsely claimed that Trezor engineers had discovered a critical hardware-level flaw in the STM32 microcontrollers used in roughly one in four Trezor devices, alleging that recovery seed phrases could be exposed to brute-force cracking due to insufficient entropy. The email urged recipients to click a link to "update" their device, a lure engineered to harvest seed phrases or otherwise compromise victims' cryptocurrency wallets.
Because the email was sent through Trezor's own breached third-party sending infrastructure rather than a spoofed look-alike domain, it passed SPF, DKIM, and DMARC authentication checks, making it significantly more convincing than typical phishing lures that rely on cosmetically similar domains. Trezor stated the email "is not coming from us, and it's a phishing attempt," instructed customers not to click any link, took down the malicious landing-page domain, and opened an investigation into how the attackers gained the ability to send mail as its official domain.
The same day, Swiss hardware wallet maker BitBox reported a near-identical phishing campaign impersonating its own brand, stating its "newsletter provider" was very likely compromised. Security researchers -- including Casa co-founder Nick Neuman and independent researcher Jameson Lopp -- publicly assessed that a single shared third-party email/marketing provider used by multiple cryptocurrency companies had likely been compromised and abused to launch coordinated phishing against both vendors' customer bases simultaneously. The specific provider has not been publicly confirmed by either Trezor or BitBox as of this writing.
The incident is the latest in a string of third-party vendor compromises reaching Trezor's customers: in January 2024 a breach of Trezor's third-party support ticketing portal exposed roughly 66,000 (later revised to 80,689) customers' names and emails and was likewise followed by phishing attempts, and in August-September 2026 a breach at fulfillment partner ShipMonk (via a critical SQL-injection flaw, CVE-2026-72898, in ShipMonk's Metabase deployment) exposed shipping and contact data for roughly 81,000 Trezor customers. While unrelated in root cause, these incidents collectively illustrate a recurring risk pattern: Trezor's own hardware and firmware are not implicated, but repeated breaches of the third-party vendors that hold or transmit Trezor customer contact data create a steady supply of credible pretexts and target lists for social-engineering campaigns against cold-storage wallet holders.
MITRE ATT&CK techniques by tactic:
Defense Evasion
T1078.004 Valid Accounts: Cloud Accounts; T1684.001 Impersonation
Initial Access
T1199 Trusted Relationship; T1566.002 Phishing: Spearphishing Link
Execution
T1204.001 User Execution: Malicious Link
Resource Development
T1583.001 Acquire Infrastructure: Domains; T1584.006 Compromise Infrastructure: Web Services; T1586.002 Compromise Accounts: Email Accounts
Reconnaissance
T1589.002 Gather Victim Identity Information: Email Addresses
Impact
Remediation
Immediate actions
- Do not click links in the 'Critical Security Alert: STM32 Entropy Vulnerability' email or any unsolicited Trezor/BitBox security alert; verify any advisory via the vendor's official app or website, never via an emailed link
- Report the phishing email to Trezor or BitBox support channels and delete it without interacting
- Never enter a seed phrase, recovery phrase, or passphrase into any web page reached via an emailed link
Workarounds
- Treat any unsolicited 'critical vulnerability' email about a hardware wallet as phishing by default; confirm real advisories only via the vendor's official app, verified social media, or its own blog domain directly
Longer-term hardening
- Vendors: audit and rotate credentials for all third-party email/marketing/newsletter platforms and enforce MFA on those accounts
- Vendors: monitor SPF/DKIM/DMARC-passing mail sent through third-party ESPs for anomalous campaign activity, not just spoofed-domain mail
- Vendors: minimize customer PII (email addresses) held by or shared with third-party marketing and fulfillment providers, and contractually enforce data deletion after a partnership ends
Affected and fixed versions
- SatoshiLabs (Trezor) — Trezor customer email communications sent via third-party email provider (help@trezor.io)
Vulnerable versions: Third-party email/marketing provider integration; exact vendor unconfirmed as of 2026-09-10
Fixed in: Malicious landing-page domain taken down by Trezor; provider-side remediation not yet publicly confirmed - BitBox (Shift Crypto) — BitBox customer newsletter/email communications
Vulnerable versions: Suspected shared third-party newsletter provider; exact vendor unconfirmed
Fixed in: Not publicly confirmed
Timeline
- Trezor discloses unauthorized access to its third-party support ticketing portal, later found to affect roughly 66,000 (revised to 80,689 in March 2024) customers' names and emails; the exposure was followed by phishing attempts against affected users.
- Trezor's fulfillment/logistics partner ShipMonk notifies Trezor of unauthorized access to its systems, exploiting a critical SQL-injection flaw (CVE-2026-72898, CVSS 10.0) in ShipMonk's Metabase analytics deployment.
- Trezor publicly discloses the ShipMonk breach, initially affecting close to 14,000 customers' shipping addresses, names, emails, and phone numbers.
- ShipMonk informs Trezor that the breach also exposed historical order data from a prior partnership period (November 2019 - August 2021) that should have been deleted.
- Trezor updates its disclosure: the ShipMonk breach total reaches roughly 81,000 customers (about 67,000 additional US customers) after ShipMonk failed to delete retained data per its contract with Trezor.
- Security researchers (Casa's Nick Neuman, independent researcher Jameson Lopp) and multiple outlets report the Trezor and BitBox phishing emails passed SPF/DKIM/DMARC checks and were likely sent via a shared, compromised third-party marketing/email provider used by several cryptocurrency companies.
- Trezor takes down the malicious domain linked from the phishing email and opens an investigation into how attackers gained the ability to send mail as its official domain.
- Trezor warns customers that its third-party email provider was breached and used to send a phishing email titled 'Critical Security Alert: STM32 Entropy Vulnerability' from the legitimate locked-ioc-1 address, falsely claiming an STM32 microcontroller entropy flaw could expose seed phrases to brute-force attack.
- BitBox's preliminary review concludes it is very likely that its newsletter/email provider was compromised.
- BitBox posts an early-morning warning on X that a phishing email impersonating BitBox is circulating and opens an investigation.
Sources cited
- Explained: The Trezor/ShipMonk Breach (August 2026) halborn.com · Research · 2026-08-15
- Trezor security alert: Stay vigilant against a potential phishing attack blog.trezor.io · Vendor report · 2024-01-20
- Trezor warns users of email provider breach, phishing attacks BleepingComputer · News · 2026-09-10
- Trezor says third-party security breach led to phishing emails from legitimate domain theblock.co · News · 2026-09-09
- Bitcoin Wallet Maker Trezor Says Hackers Breached Its Email Provider decrypt.co · News · 2026-09-10
- Fake Security Emails Target Trezor and BitBox Users cointelegraph.com · News · 2026-09-10
- Multiple hardware crypto wallet providers warn of phishing emails after third-party incident cyberdaily.au · News · 2026-09-10
- Trezor data breach impact now reaches 81,000 customers BleepingComputer · News · 2026-09-04
- Trezor support site breach exposes personal data of 66,000 customers BleepingComputer · News · 2024-01-19
- Trezor (@Trezor) official statement on X x.com · News · 2026-09-10
Previous and next in phishing
Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated —.