Former Revolut Employee Blackmails Crypto Trader

A cryptocurrency trader named TraderSZ revealed that he was blackmailed by a former Revolut employee threatening to publish his personal information. In a message shared on the X platform on Thursday, TraderSZ stated that the employee also sent messages to his family via Revolut demanding payment. TraderSZ, who showed screenshots of correspondence with Revolut customer support, did not provide a detailed response to Cointelegraph.

Revolut’s Official Statement and Investigation

A Revolut spokesperson confirmed that they have reported the matter to legal authorities and are investigating the former employee’s illegal actions. The company stated that there was no breach in their security systems and that they are in communication with the affected customer. Revolut is a fintech platform that reached a $75 billion valuation in November 2025 and has over 65 million users.

The Danger of Wrench Attacks Targeting BTC Investors

As blackmail and “wrench attacks” (physical coercion attacks) cases targeting crypto investors increase, traders conducting BTC detailed analysis are also at risk. According to CertiK data, physical attacks rose by 75% in 2025, reaching 72. These attacks involve violent methods to seize wallet passwords.

• 2025 Statistics: 72 wrench attack cases (+75% increase)
• Highest Risk Target: High-volume BTC and crypto traders
• Precaution: 2FA and cold wallet usage are essential

For investors trading BTC futures, this incident underscores the importance of platform security. Physical threats are harder to prevent than digital security.

Frequently Asked Questions About the Revolut Blackmail Incident

• How much payment was demanded from TraderSZ? Details were not shared, but the threat of personal data leak was used.
• How is Revolut’s data security? The company confirmed no breach, investigation ongoing.
• How do wrench attacks affect BTC traders? Physical pressure for wallet access is increasing, CertiK reported 72 cases.
• What should users do? Strong passwords and legal reporting are recommended.