Trezor Executive Rejects ZachXBT's Criticism of Hardware Wallets
An executive at hardware wallet maker Trezor has rejected criticism of hardware wallets made by ZachXBT. The body of the provided text contains only webpage styling code (CSS) and no substantive news content, so no further details of the dispute or the executive's arguments are available from the text.
TL;DR
Trezor disclosed that attackers abused its support contact form to generate phishing emails that look like official replies. The firm says no internal systems were breached, but users must keep backups private and offline to avoid fraud.
Key facts
- Trezor warned users on July 18, 2026 about phishing emails mimicking official support replies.
- Attackers submitted fake support requests on behalf of real email addresses.
- The automated replies were generated by Trezor’s own support system.
- Trezor confirmed no breach of internal data, systems, or infrastructure.
- The company reiterated that it will never ask for a wallet backup via email.
Trezor, the hardware wallet maker, issued a warning on July 18, 2026 that attackers were exploiting its customer‑support contact form to send phishing emails that appear to come from official Trezor support. The fraudulent messages were automated replies triggered by fake support requests submitted on behalf of real users. Trezor emphasized that it never asks for wallet backups and that the contact form remains secure, while noting that no internal systems were compromised.
Background
Hardware wallets such as Trezor are a cornerstone of crypto security, storing private keys offline to protect users from online attacks. Over the past year, phishing campaigns have surged across the cryptocurrency ecosystem, targeting both retail users and high‑net‑worth individuals. Recent incidents include a venture‑capital partner losing a large portion of his life savings to a spear‑phishing attack, a victim being scammed twice in three hours for a total of $2.6 million in stablecoins, and malicious pop‑up notifications on sites like CoinMarketCap and Cointelegraph that prompted users to verify wallets. These attacks often leverage trusted brand names to increase credibility, making it harder for recipients to distinguish genuine communications from fraud. The broader industry has seen similar threats against other hardware wallet providers, such as Ledger, where fake apps have been used to steal seed phrases. In this environment, any misuse of a legitimate support channel can amplify the reach of phishing scams, as automated replies can be crafted to look authentic while the underlying request originates from an attacker. Trezor’s response highlights the importance of maintaining strict controls over support interactions and reinforcing user education about never sharing backups or private keys.
What happened
On July 18, 2026 Cointelegraph reported that Trezor warned users about an ongoing phishing campaign that mimics the company’s official customer‑support replies. The warning was posted on a Monday X (formerly Twitter) message, stating that attackers abused Trezor’s contact form to send scam emails appearing as legitimate support replies. According to the Trezor spokesperson quoted by Cointelegraph, the attackers submitted fake support requests on behalf of the email addresses of the recipients, which triggered an automated response from the official support system. The company clarified that the contact form remains safe and secure, and that no breach of internal data, systems, or infrastructure occurred. Trezor also reminded users that wallet backups must always stay private and offline, and that the firm will never ask for a backup via email. The spokesperson added that the attackers were able to manipulate the email subject line but could not compromise any Trezor systems. The article also referenced broader phishing trends, noting that similar attacks have affected platforms like CoinMarketCap and Cointelegraph, and that high‑value victims have lost millions in stablecoins due to spear‑phishing. Trezor concluded that the issue has now been contained, emphasizing that the automated replies were the result of the attackers’ misuse of the support form rather than a direct hack of Trezor’s infrastructure.
Market impact
The source does not provide direct cryptocurrency price data or market‑wide flow figures linked to the Trezor phishing incident. However, it does reference a $2.6 million loss suffered by a victim of a separate phishing attack in late May, illustrating the potential financial impact of such scams on individual investors. The article also mentions that CoinMarketCap removed a malicious pop‑up notification and that Cointelegraph experienced a brief compromise of its banner publishing system, both of which were quickly resolved. While no specific price movements are cited, the repeated mention of phishing attacks across the industry underscores a persistent risk factor that can influence investor confidence and potentially affect trading volumes on platforms that host vulnerable users.
Why it matters
The incident matters because it demonstrates how attackers can weaponize a legitimate support channel to amplify phishing campaigns without breaching core systems. By submitting fake requests, they trigger official‑looking automated replies that can deceive users into revealing sensitive information, such as wallet backups, which Trezor explicitly states it will never request. This method sidesteps traditional email‑spoofing defenses, as the messages originate from Trezor’s own servers. The broader context of high‑value phishing losses, including the $2.6 million scam, highlights the financial stakes for users who rely on hardware wallets for security. Moreover, the episode reinforces the need for continuous user education about the immutable rule that backups must stay offline and never be shared, even when an email appears to come from a trusted source. For the crypto ecosystem, such attacks erode trust in service providers and can prompt tighter security measures, influencing how platforms design support workflows and communicate with users.
DeFi Intel’s take
Editorial analysis, not a statement of fact.
DeFi Intel's take: the Trezor episode suggests that attackers are shifting toward exploiting automated support mechanisms rather than attempting direct system breaches. We read this as a sign that phishing operators are refining their tactics to increase credibility while minimizing technical risk. The fact that Trezor could contain the issue quickly and affirm that its contact form remains secure indicates that internal safeguards are effective, but the incident also underscores the importance of user vigilance. As phishing continues to target high‑value crypto holders, the industry may see more emphasis on multi‑factor verification for support interactions and broader educational campaigns reminding users that no legitimate entity will ever request a wallet backup via email.
Sources used for this analysis
DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.
Frequently asked questions
How did attackers send phishing emails that looked like Trezor support?
Attackers submitted fake support requests on behalf of real users through Trezor’s contact form. This triggered the platform’s automated reply system, which sent emails that appeared to come from official Trezor support. The attackers could also manipulate the email subject line, making the messages seem authentic.
Did the phishing campaign compromise any Trezor internal systems?
Trezor confirmed that no internal data, systems, or infrastructure were compromised. The phishing emails resulted from the misuse of the contact form, not from a breach of Trezor’s servers or databases.
What should users do if they receive an email asking for their wallet backup?
Users should remember that Trezor will never ask for a wallet backup via email. Backups must stay private and offline. If such a request is received, it should be treated as a phishing attempt and reported to Trezor’s official channels.
Direct answers
Short answers, written to be quoted.
- What is Trezor’s policy on requesting wallet backups?
- Trezor says it will never ask for a wallet backup via email and that backups must always remain private and offline.
DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Binance_intel.
Entities in this story
Discussion
Comments are reviewed before publication.
Want the full article?
Continue reading on Binance_intel →
No comments yet.