Rkit
Table of Contents
Overview
Rootkit:Win32/Rkit is a generic detection name used by Microsoft Defender to identify advanced, highly privileged malware known as **Rootkits**. Unlike a standard trojan that operates in User Mode (Ring 3), a true rootkit executes in Kernel Mode (Ring 0), granting it absolute authority over the Windows operating system. Its primary purpose is not necessarily payload delivery, but **total stealth**: subverting the OS itself to hide files, processes, registry keys, and network connections from standard antivirus software, EDR sensors, and even the system administrator.
Understanding Rkit (Rootkits)
To an end-user, a rootkit infection is completely invisible; the computer may function normally, or only slightly slower. For a security analyst, a rootkit represents the ultimate compromise. Because the rootkit lives at a lower level than the antivirus software, it can intercept the API calls the antivirus makes to scan the disk, feeding it 'clean' data while hiding the malicious files. Detecting a rootkit requires specialized tools that look for anomalies and unhooked APIs, or analyzing the system from an offline environment.
Execution and Stealth Mechanics
Rkit variants are deployed post-exploitation, requiring administrative or SYSTEM privileges to install (`T1543.003`). Once executed, they typically employ techniques like System Service Descriptor Table (SSDT) Hooking (`T1014`) or Direct Kernel Object Manipulation (DKOM). By hooking the SSDT, the rootkit intercepts fundamental system calls (like `NtQuerySystemInformation`, used by Task Manager to list processes). When the OS asks 'What processes are running?', the rootkit modifies the response to remove its own process ID before handing the list back to the OS. DKOM involves directly modifying the `EPROCESS` structures in memory to unlink a running process from the active process list, making it entirely invisible to standard tools (`T1564`). Rootkits also frequently hook the NDIS (Network Driver Interface Specification) layer to hide their outbound C2 communications (`T1562.001`).
Indicators of Compromise & Impact
The impact is total loss of system trust. Host-based IoCs are extremely difficult to spot from a live system. Indicators include discrepancies between different types of system API calls (e.g., cross-view analysis where tool A sees a file, but tool B does not), unsigned or suspicious `.sys` drivers loaded into memory, and EDR alerts regarding SSDT modifications or patching of `ntoskrnl.exe`. Network IoCs (beaconing traffic) may still be visible at the firewall, even if they are hidden on the host.
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 |
|---|---|---|---|
T1014 | Rootkit (Hooking kernel APIs and SSDT) | Defense Evasion | ATT&CK ↗ |
T1564 | Hide Artifacts (DKOM to hide processes) | Defense Evasion | ATT&CK ↗ |
T1543.003 | Create or Modify System Process: Windows Service (Loading malicious drivers) | Persistence | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools (Subverting AV sensors) | Defense Evasion | ATT&CK ↗ |
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-KMC | Kernel Memory Integrity Checking | Harden | T1014 | Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution. |
D3-SCM | Windows Service Creation Monitoring | Detect | T1543.003 | Verify service binary image signatures and restrict standard users from creating or modifying service definitions. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_RKIT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Rkit"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "rkit" 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 - Rkit (Trojan) Execution & Triage
id: 105e862f-7265-5666-8a36-e9dfebe62b85
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Rkit 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/rkit
- 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.t1014
- attack.t1562_001
- attack.t1564
- attack.t1543_003
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_RKIT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Rkit 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 = "rkit" 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.
- Physically disconnect the compromised endpoint from the network; since the host is untrustworthy, you cannot rely on software firewalls to block its traffic.
- Do NOT attempt to clean a confirmed kernel-level rootkit; the only remediative action is a complete wipe and reimage of the hard drive.
- To perform forensics, you must boot the machine from a known-good Live CD/USB or mount the hard drive externally to bypass the rootkit's API hooks.
- Investigate how the attacker gained the necessary administrative or SYSTEM privileges required to install the kernel driver in the first place.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not trust the output of standard tools (Task Manager, netstat, even some local EDR queries) on a machine suspected of harboring a rootkit.
- Avoid leaving Secure Boot disabled in the BIOS/UEFI, as Secure Boot is a primary defense against the loading of unsigned, malicious rootkit drivers.
References & External Analysis
- Search "rkit" on VirusTotal (External Analysis)
- Search "rkit" on Any.Run (Sandbox Sandbox)
- Search "rkit" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Rkit and what threat category does it belong to?
Rkit 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 Rkit establish persistence and evade defensive controls?
Rkit 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 Rkit compromise?
Security teams responding to Rkit 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 Rkit?
Rkit 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 Rkit across enterprise endpoints?
Defenders should hunt for Rkit 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 Rkit Trojan from Windows?
Manual removal of Rkit 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 Rkit a virus or a Trojan?
Rkit is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Rkit typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Rkit infection?
Symptoms of Rkit 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 Rkit 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/rkit.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.