A recent investigation by Palo Alto Networks' Unit 42 has exposed a long-running and extensive cybercrime operation tracked as CL-CRI-1171. This threat cluster operates a sophisticated pay-per-install (PPI) service, leveraging popular platforms like YouTube and search engine optimization (SEO) poisoning to achieve widespread infections. The campaign has been active for at least two years, successfully compromising both individual gamers and high-value targets within corporate, government, and critical infrastructure sectors.
The operation's effectiveness stems from its use of a generic, custom-built loader that appears as unremarkable commodity malware, thus avoiding deeper security analysis. This loader serves as a delivery mechanism for a rotating bundle of payloads from various cybercriminal clients. Analysis revealed the distribution of several malware families, including the newly identified Insomnia RAT and the previously undocumented ARKTunnel and Docro Hijacker malware. The infrastructure supporting this campaign is vast, involving over 10,000 loader samples and more than 200 rotational command-and-control (C2) domains, highlighting the scale and persistence of this threat.
The CL-CRI-1171 operation functions as a Malware-as-a-Service (MaaS) platform, specifically a PPI network. The operators provide an infection service to other threat actors, who pay to have their own malicious payloads distributed to a wide audience. The investigation was triggered by two seemingly routine infections at separate organizations that shared an identical, untracked loader, which led to the discovery of the broader campaign.
Key components of the threat include:
Infection Vectors: The group employs a two-pronged approach to lure victims:
Payload Delivery: A single, custom loader is used across all infection vectors. This loader is designed to be disposable and is capable of fetching and executing multiple, unrelated malware payloads on a compromised system. This means a single infection can result in the deployment of a backdoor, a data hijacker, and other threats simultaneously, each with its own objectives and C2 infrastructure.
The core of the CL-CRI-1171 operation is its shared infrastructure, which allows it to scale effectively while remaining difficult to track.
The primary common denominator is a custom loader, with over 10,000 unique samples identified. This loader is responsible for the initial compromise and subsequent download of additional payloads. It communicates with a sprawling C2 network characterized by:
bubbleslip, churchpail, dinosaursjam)..xyz, .cfd, .space, and .info top-level domains.This rotational infrastructure makes blocklisting based on individual domains ineffective.
The PPI model allows for a flexible and rotating set of payloads. While the investigation identified a core bundle in rotation from July 2025 to April 2026, other malware families were also observed. The analyzed payloads include:
The tactics, techniques, and procedures (TTPs) observed or inferred in this campaign include:
The CL-CRI-1171 campaign poses a significant risk due to its broad targeting and deceptive nature. The impact extends beyond the initial infection:
No specific file hashes, IP addresses, or domains were provided in the source article. However, the report describes the C2 domain structure.
[two-word-compound]bubbleslip or dinosaursjam..xyz, .cfd, .space, .infoSecurity teams can hunt for potentially related activity using the following patterns:
WinDirStat_setup.exe, bluetooth_driver_installer.exe(word1)(word2).xyz(word1)(word2).cfdHTTP/S POST to *.xyzDetecting and responding to this threat requires looking beyond surface-level indicators.
.xyz, .cfd, .space, .info), especially when combined with unusual domain name patterns. Use Network Traffic Analysis to baseline normal activity and spot anomalies.Defending against this multi-faceted threat requires a layered security approach.
.xyz and .cfd for high-risk user groups.Train users to recognize and avoid social engineering tactics like those used on YouTube and through SEO poisoning, and to only download software from official sources.
Filter and monitor outbound network traffic to block connections to known malicious domains and suspicious TLDs (.xyz, .cfd, etc.) used by the C2 infrastructure.
Use web filtering and URL analysis to block users from accessing malicious links and downloading files from untrusted sources.
Implement application control policies, such as executable allowlisting, to prevent the execution of unauthorized and potentially trojanized software.
Deploy and maintain endpoint protection solutions to detect and quarantine the loader and its subsequent payloads based on signatures and behavioral analysis.
To counter the CL-CRI-1171 threat, organizations should implement robust Network Traffic Analysis (NTA). This involves deploying sensors at key network egress points to monitor all outbound traffic. The primary goal is to detect the loader's C2 communications. Configure NTA tools and SIEM to specifically alert on DNS queries and HTTP/S connections to the TLDs favored by this group: .xyz, .cfd, .space, and .info. Create rules that correlate this with domain names that fit the two-word compound pattern observed in the campaign. Establish a baseline of normal outbound traffic for workstations and servers. An alert should be triggered when a user workstation, after downloading a new executable, initiates connections to a newly observed domain on one of these TLDs. This technique is critical for detecting active infections that have bypassed endpoint controls, providing a chance to intervene before secondary payloads like Insomnia RAT can be downloaded and activated.
Executable Allowlisting is a highly effective countermeasure against the CL-CRI-1171's infection vectors. Since the attack relies on tricking users into running a trojanized executable (e.g., a fake WinDirStat installer), a properly configured allowlisting policy would prevent the malicious file from running in the first place. Organizations should deploy solutions like Windows Defender Application Control or AppLocker. Start by running in audit mode on a representative group of systems to build a baseline of legitimate applications and installers. Once the baseline is established, switch to enforcement mode. For developer or IT administrator machines that require more flexibility, use a managed installer model where all new software must be deployed through a trusted, centralized software management system. This directly mitigates the risk from both the SEO poisoning and YouTube lure vectors by ensuring only vetted and approved executables can run, regardless of how they arrive on the endpoint.
Leveraging Process Analysis via an EDR solution is crucial for detecting the post-execution behavior of the CL-CRI-1171 loader. Even if the initial binary is not detected by signature, its actions can betray its malicious nature. Security teams should configure EDR policies to monitor for suspicious process parent-child relationships. For example, an alert should be generated if a process associated with a web browser (chrome.exe, firefox.exe) spawns a downloaded executable that in turn spawns a command shell (cmd.exe) or PowerShell (powershell.exe) to make outbound network connections. Specifically for this threat, create detection rules that look for any process making network connections to the suspicious TLDs (.xyz, .cfd, etc.). This behavioral approach is resilient to the threat actor's use of over 10,000 unique loader samples, as the fundamental behavior of 'download and execute' remains consistent. This allows for detection even when the specific file hash is unknown.
CL-CRI-1171 cybercrime operation is estimated to have begun, operating for at least two years prior to the report.
The payload rotation including Insomnia RAT, ARKTunnel, and Docro Hijacker was observed to be active.
Unit 42 investigates two separate incidents involving the same loader, which delivered Insomnia RAT, ARKTunnel, and Docro Hijacker.
A subsequent infection was observed where the loader delivered two different payloads: GCleaner and Socks5Systemz.
Unit 42 publishes its research on the CL-CRI-1171 pay-per-install network.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.