Crypto: Trezor Warns Against Fake Support Emails

A new crypto alert is shaking the hardware wallet user community. Trezor, one of the industry leaders, has fallen victim to a phishing attack via its own customer support. All the details in the following paragraphs!

A Sophisticated Crypto Attack Targets Trezor

Monday morning, Trezor published an official warning for its community. Hackers indeed managed to hijack the contact form on the official website to make it appear as legitimate responses from customer support. These fake emails appeared authentic and urged victims to share their wallet backup.

The company clarifies that no email leaks occurred and the system was not hacked in the strict sense. In reality, hackers sent messages to support while spoofing addresses of users already known through previous leaks (at Mailchimp or elsewhere). This triggered an “official” automatic response. A simple but deadly mechanism!

The company claims to have secured the affected channel. It is actively seeking solutions to prevent any future hijacking.

Social Engineering, the New Weapon of Crypto Scams

This case recalls previous incidents in the crypto world, notably with Ledger. The crypto company suffered a massive leak in 2020. Waves of phishing followed, targeting thousands of investors through emails and fake support. More recently, MetaMask and Trust Wallet users have also been victims of similar attempts.

The real threat here does not come from a technical flaw, but psychological manipulation. By exploiting users’ trust in customer support, fraudsters indeed play on panic and urgency. Once the backup is provided, access to crypto funds is total.

The lesson? Even without a technical breach, scammers adapt their methods. Education, vigilance, and offline data protection remain the best defenses in the cryptographic universe.

This attack without direct hacking shows that social engineering has become one of the most powerful weapons against crypto investors. Vigilance is therefore essential, even when everything seems secure.