Security

Crypto Clipper Malware Uses Tor and USB Worm Spread

3 min read

Summary

Microsoft has detailed a Windows-based crypto clipper campaign that uses malicious shortcut files, a bundled Tor client, and worm-like USB propagation to steal wallet data and maintain persistence. The threat matters because it combines clipboard theft, screenshot exfiltration, and remote code execution with stealthy Tor-based command and control, making behavioral detection critical for defenders.

Need help with Security?Talk to an Expert

Introduction

Microsoft Threat Intelligence has published details on a Windows-based crypto clipper campaign active since February 2026. While crypto clippers are typically associated with wallet address replacement, this threat is more advanced: it uses Tor for hidden command-and-control, spreads through USB devices, and behaves like a lightweight backdoor.

For security teams, this is important because the malware avoids traditional installer patterns and IP-based infrastructure, making behavioral detection and endpoint visibility especially important.

What’s new

Tor-backed command and control

  • The malware launches a bundled Tor client, renamed ugate.exe.
  • It routes traffic through localhost:9050 using a local SOCKS5 proxy.
  • C2 communication happens over .onion services, reducing DNS and destination visibility.

Worm-like USB propagation

  • Initial access starts with malicious .lnk shortcut files distributed on USB storage.
  • The malware hides legitimate files and replaces them with lookalike shortcut files.
  • It creates scheduled tasks to continue spreading to newly inserted USB devices.

Clipper and stealer behavior

  • The malware monitors the clipboard about every 500 milliseconds.
  • It looks for wallet addresses, BIP39 seed phrases, and private keys.
  • It can replace copied cryptocurrency wallet addresses with attacker-controlled values.
  • It also captures and uploads screenshots for additional context.

Backdoor capability

  • The malware polls its C2 for commands.
  • An EVAL instruction allows attacker-supplied JScript code to run at runtime.
  • This turns the clipper into a lightweight remote access tool, not just a financial stealer.

Why this matters for defenders

This campaign blends multiple techniques that can bypass simple signature-based controls. The use of Windows Script Host, ActiveX, scheduled tasks, Defender exclusions, and Tor makes it harder to spot through conventional indicators alone.

Microsoft says the strongest signals are behavioral, including:

  • Script interpreters spawning unusual child processes
  • Use of 127.0.0.1:9050 or localhost SOCKS5 activity
  • PowerShell screen-capture behavior
  • Clipboard inspection or crypto-address replacement patterns

Microsoft Defender for Endpoint detects related activity such as Suspicious JavaScript process and Possible data exfiltration using Curl. Microsoft Defender Antivirus detects the threat as Trojan:Win32/CryptoBandits.A.

  • Block or tightly control execution of .lnk files from USB media.
  • Monitor for WScript, curl, and Tor-related processes on endpoints.
  • Review scheduled tasks and unusual files under C:\Users\Public\Documents.
  • Investigate systems showing localhost:9050 traffic or hidden Tor usage.
  • Ensure Microsoft Defender protections and endpoint detection rules are up to date.

Organizations with users handling cryptocurrency or seed phrases should treat this campaign as a high-priority risk due to its theft, persistence, and remote execution capabilities.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

crypto malwareTorUSB wormMicrosoft Defenderclipboard theft

Related Posts

Security

Microsoft Digital Defense Report 2026: Key Security Insights

Microsoft's 2026 Digital Defense Report highlights how AI and growing system interconnectedness are reshaping both cyberattacks and defense strategies. The report emphasizes that organizations must secure AI, identities, data, and cloud environments together while improving signal correlation across tools to detect modern threats faster.

Security

Government Cyber Risk in 2026: Microsoft’s 5 Priorities

Microsoft says government agencies were the most targeted sector in 2026, accounting for 27% of observed cyber threat activity. The company urges public-sector leaders to focus on five resilience priorities, including faster response, AI security, bidirectional information sharing, and planning for incidents that spread across suppliers and essential services.

Security

Microsoft Ignite 2026 Security Guide: Key Sessions

Microsoft has published its security guide for Microsoft Ignite 2026, highlighting AI-first security themes, a dedicated Security Pre-Day, and technical sessions focused on securing identities, data, devices, clouds, and AI agents. For IT and security teams, the event offers an early look at Microsoft’s roadmap and practical guidance for building an AI-ready security strategy.

Security

CVE-2026-73570: Zimbra Mail Server Exploitation

Microsoft is tracking active exploitation of CVE-2026-73570, an unauthenticated command injection flaw affecting internet-facing Zimbra mail servers with the optional zimbra-snmp package installed and SNMP notifications enabled. The issue can lead to web shell deployment, privilege escalation, mailbox data theft, and persistent remote access, making immediate patching and configuration review critical for administrators.

Security

Phishing Abuses RMM Tools for Persistent Access

Microsoft security researchers observed phishing campaigns in July 2026 that used a legitimate MSP360 RMM installer disguised as meeting invites, PDF updates, and other lures to gain remote access. Attackers then deployed ConnectWise ScreenConnect for redundant persistence, highlighting the need for tighter controls on remote management tools and better detection of unapproved RMM activity.

Security

Azure DevOps Attack Path Exposed in New DART Report

Microsoft’s latest DART cyberattack report shows how a single compromised identity was used to access Azure DevOps, alter pipelines, and harvest Kubernetes credentials. The case highlights how tightly connected identity, DevOps, and cloud environments can let attackers move far beyond source code, making stronger identity and pipeline controls essential.