Rockrat
Table of Contents
Overview
Backdoor:Win32/Rockrat is a specific family of Remote Access Trojan (RAT) designed to provide a threat actor with complete, interactive control over a compromised Windows endpoint (`T1059`). Like many modern RATs, Rockrat is often deployed as a secondary payload after an initial breach, allowing attackers to exfiltrate data, monitor user activity, and pivot laterally across the corporate network.
Understanding Rockrat (Remote Access)
To an end-user, the computer functions normally, though it may occasionally feel sluggish. For a SOC analyst, a Rockrat detection is a high-severity alert indicating an active, human-driven intrusion. An attacker sitting at a remote console is using Rockrat to interact with the machine in real-time, completely bypassing standard authentication controls.
Execution and Control Mechanics
Once deployed, Rockrat typically establishes persistence via standard Registry Run keys or hidden scheduled tasks (`T1547.001`). It then initiates a persistent, outbound connection to its Command and Control (C2) server (`T1071.001`). The RAT provides a suite of capabilities to the attacker: opening a hidden command shell (`cmd.exe`), capturing keystrokes (`T1056.001`), taking screenshots, downloading/uploading files, and sometimes activating the webcam or microphone.
Indicators of Compromise & Impact
The impact is total loss of confidentiality and integrity for the compromised host. Host-based IoCs include unknown executables running from `%AppData%` or `%Temp%` making continuous outbound network connections. EDR logs may show Rockrat spawning `cmd.exe` to execute administrative commands (like `net user` or `ping`) or reading sensitive files. Network IoCs are characterized by long-lived TCP sessions with beaconing behavior to suspicious IP addresses or dynamic DNS domains.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
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-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_ROCKRAT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Rockrat"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "rockrat" 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 - Rockrat (Trojan) Execution & Triage
id: 5e1227f1-794d-59a9-9cb0-4842aa6192f9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Rockrat 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/rockrat
- 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.t1059_003
- attack.t1056_001
- attack.t1547_001
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: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_ROCKRAT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Rockrat 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 = "rockrat" 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.
- Isolate the endpoint immediately to sever the attacker's interactive connection and prevent data exfiltration.
- Analyze EDR and command-line logs to determine exactly what actions the attacker performed while the RAT was active (e.g., did they dump LSASS?).
- Identify the C2 domain/IP address the RAT was communicating with and block it at the perimeter.
- Assume any credentials typed on the infected machine are compromised and force a password reset.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not leave the machine on the network to 'monitor' the attacker; they can rapidly deploy ransomware if they sense they are being watched.
- Avoid trusting the integrity of the operating system after a RAT infection; the machine should be completely wiped and re-imaged.
References & External Analysis
- Search "rockrat" on VirusTotal (External Analysis)
- Search "rockrat" on Any.Run (Sandbox Sandbox)
- Search "rockrat" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Rockrat and what threat category does it belong to?
Rockrat 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 Rockrat establish persistence and evade defensive controls?
Rockrat 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 Rockrat compromise?
Security teams responding to Rockrat 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 Rockrat?
Rockrat 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 Rockrat across enterprise endpoints?
Defenders should hunt for Rockrat 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 the Rockrat Trojan from Windows?
Manual removal of Rockrat 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.
Is Rockrat a virus or a Trojan?
Rockrat is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Rockrat typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Rockrat infection?
Symptoms of Rockrat 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 Rockrat 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/rockrat.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.