Cliptoshuffler
Table of Contents
Overview
Executive Summary
Cliptoshuffler (often referred to simply as a "Clipper") is a highly specialized and stealthy Trojan engineered specifically to steal cryptocurrency. It operates by continuously monitoring the infected system's clipboard. When it detects a string resembling a cryptocurrency wallet address, it instantly replaces it with a wallet address controlled by the attacker, hijacking the transaction before it is sent.Infection Vector and Technical Capabilities
Clippers are frequently bundled with other malware, distributed via Malspam, hidden inside "cracked" software, or dropped by initial access brokers who have already compromised a system. Once resident in memory, Cliptoshuffler executes its targeted theft routine:- Clipboard Hooking: The malware utilizes Windows APIs (such as `SetClipboardViewer` or polling the clipboard via `GetClipboardData`) to continuously monitor any text copied by the user.
- Pattern Matching: The Trojan contains a list of Regular Expressions (Regex) designed to identify the distinct formats of various cryptocurrency addresses, including Bitcoin (starting with 1, 3, or bc1), Ethereum (starting with 0x), Litecoin, and Monero.
- On-the-Fly Substitution: When a user copies a legitimate recipient address to paste it into their wallet software or an exchange portal, Cliptoshuffler instantly overwrites the clipboard contents with the attacker's corresponding address. If the user fails to double-check the pasted address before authorizing the transaction, the funds are irreversibly sent to the attacker.
Threat Assessment
A Cliptoshuffler infection leads to immediate, irreversible financial loss. Because cryptocurrency transactions cannot be reversed or charged back, the theft is absolute. The malware is designed to be entirely invisible to the user until the moment the transaction is finalized.Remediation and Eradication
- Endpoint Scanning: Utilize an enterprise-grade anti-malware solution to perform a full system scan. Clippers often lack complex obfuscation but hide deep within system processes or as scheduled tasks.
- Transaction Verification Procedures: The most effective defense against clippers is procedural: users must be trained to manually verify the first and last several characters of a cryptocurrency address after pasting it into the destination field and before clicking send.
- Comprehensive Review: The presence of a clipper often indicates a broader compromise. A full forensic review of the endpoint should be conducted to ensure no secondary backdoors or info-stealers were deployed alongside the clipper.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1115 | Clipboard Data | Collection | ATT&CK ↗ |
T1565.001 | Data Manipulation: Stored Data Manipulation (Altering DNS IP settings) | Impact | ATT&CK ↗ |
T1059 | Command and Scripting Interpreter | Execution | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-SEA | Script Execution Analysis | Detect | T1059 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
D3-CAC | Clipboard Access Control | Isolate | T1115 | Isolate virtual desktop infrastructure (VDI) clipboards and alert on rapid background clipboard querying by non-foreground processes. |
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_CLIPTOSHUFFLER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Cliptoshuffler"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "cliptoshuffler" ascii wide nocase
$s2 = "trojan.clipper" ascii wide nocase
$s3 = "trojan.cointhief" ascii wide nocase
$s4 = "win32/cliptoshuffler" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Cliptoshuffler (Trojan) Execution & Triage
id: e809a8eb-41b1-5235-8075-02feacd8983b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Cliptoshuffler malware family. Detects suspicious execution from temporary
user directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/cliptoshuffler
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1115
- attack.t1565_001
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_CLIPTOSHUFFLER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Cliptoshuffler tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "cliptoshuffler" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Cliptoshuffler from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Cliptoshuffler into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Cliptoshuffler persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Cliptoshuffler execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Cliptoshuffler dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Cliptoshuffler until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "cliptoshuffler" on VirusTotal (External Analysis)
- Search "cliptoshuffler" on Any.Run (Sandbox Sandbox)
- Search "cliptoshuffler" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Cliptoshuffler and what threat category does it belong to?
Cliptoshuffler is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Cliptoshuffler establish persistence and evade defensive controls?
Cliptoshuffler typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Cliptoshuffler compromise?
Security teams responding to Cliptoshuffler should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Trojan.Clipper?
Trojan.Clipper frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Trojan.Clipper across enterprise endpoints?
Defenders should hunt for Trojan.Clipper by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove Cliptoshuffler from Windows?
Manual removal of Cliptoshuffler is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Cliptoshuffler infection?
Symptoms of Cliptoshuffler can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Trojans
Want to prevent Cliptoshuffler and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/cliptoshuffler.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.