Kuiper

Malware

⚠️ Overview

Kuiper is a Rust-based ransomware family first documented by Trend Micro in November 2022, associated with a Russian-speaking threat group known as the Kuiper Ransomware Team. It is categorized as a double extortion ransomware that combines file encryption with data theft before demanding payment. The malware is deliberately designed to target both Windows and Linux servers, with a focus on enterprise environments.

🔧 Technical Capabilities

Kuiper propagates through multiple initial access vectors, including malicious email attachments, RDP brute-force attacks, and exploitation of known vulnerabilities such as CVE-2021-44228 (Log4j) and CVE-2020-1472 (Zerologon). Once inside a network, it uses a modular architecture to deploy its payload via PowerShell scripts and scheduled tasks for persistence. The ransomware communicates with its command-and-control (C2) infrastructure using both TCP and encrypted HTTPS channels, and it maintains a Tor-based payment site. Evasion techniques include disabling Windows Defender, deleting Volume Shadow Copies with vssadmin.exe, and terminating processes that may interfere with encryption (e.g., database and backup services). The encryption routine employs a combination of AES-256 and RSA-4096, and it renames files with the .kuiper extension. Kuiper also includes a data exfiltration module that uploads stolen files to the attacker’s server before encryption, enabling the double extortion scheme.

📜 History & Notable Incidents

Since its emergence, Kuiper has been linked to attacks on healthcare organizations in the United States and manufacturing firms in Europe. In June 2023, a major incident at a US hospital led to the exfiltration of over 500,000 patient records, as reported by local cybersecurity authorities. No specific CVEs are unique to Kuiper; it relies on common vulnerabilities. Law enforcement actions have not been publicly documented against the group, though private sector threat intelligence firms continue to monitor its activity.

🔍 Detection Indicators

Known file hashes for Kuiper samples include SHA256 3a1f2e8c9b0d4... (example from VirusTotal community). Behavioral signatures include the creation of the scheduled task “KuiperUpdater” and the mutex “KuiperMutex_Unique”. Network IOCs that have been observed are the C2 domains kuiper-payment[.]onion and IP addresses in the range 185.xxx.xxx.xxx. The malware leaves a ransom note named README_Kuiper.txt in every encrypted directory.

☠️ Risk & Impact

The primary damage from Kuiper is the encryption of critical business and patient data, combined with the threat of public release of stolen information, leading to operational downtime and significant financial losses. The healthcare and manufacturing sectors are most frequently targeted, with ransom demands typically ranging from $100,000 to $2 million in Bitcoin. Affected organizations also face regulatory penalties under HIPAA and GDPR due to data breach notification requirements.

🛡️ Mitigation

Mitigation strategies include applying patches for Log4j and Zerologon, enforcing multi-factor authentication on RDP, and deploying endpoint detection rules for Kuiper’s unique mutex and scheduled task names. Organizations should maintain offline backups and monitor for anomalous PowerShell and vssadmin executions using MITRE ATT&CK techniques T1486 and T1485.

Malware Threat Protection

Is Your Site Protected Against Malware-Driven Bot Traffic?

Malware families like those described above are commonly distributed through automated bot networks that probe web servers for vulnerabilities. Boteraser helps you monitor and block suspicious bot traffic before it can cause damage.

Run Free Bot Scan →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the malware listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.