Ntrootkit

Category: rootkit · Aliases: Rootkit:Win32/NTRootkit, Win32/NTRootkit, Rootkit.NTRoot, NTRoot Kernel Driver, Trojan:Win32/NTRootkit · Sample count (EMBER 2018): 17 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: RootkitStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
NTRootkit (classified across cybersecurity vendors as Rootkit:Win32/NTRootkit, Trojan:Win32/NTRootkit, and Rootkit.Win32.NTRoot) is an evasive stealth rootkit engineered for 32-bit and 64-bit Windows NT architecture operating systems.

Table of Contents

Overview

NTRootkit (classified across cybersecurity vendors as Rootkit:Win32/NTRootkit, Trojan:Win32/NTRootkit, and Rootkit.Win32.NTRoot) is an evasive stealth rootkit engineered for 32-bit and 64-bit Windows NT architecture operating systems. Designed to operate at kernel privilege level (Ring 0) and high user-mode levels (Ring 3), NTRootkit alters operating system behaviors to cloak malicious software presence from administrators, incident response investigators, and antivirus software. NTRootkit leverages techniques including System Service Dispatch Table (SSDT) hooking, Direct Kernel Object Manipulation (DKOM), and I/O Request Packet (IRP) major function table modification. By intercepting core Windows Native API calls (such as NtQuerySystemInformation, NtQueryDirectoryFile, and NtOpenKey), NTRootkit dynamically removes malware processes, dropped binaries, network ports, and autostart registry entries from standard administrative queries. Additionally, NTRootkit provides privileged memory execution primitives and stealth backdoors allowing threat actors to maintain deep persistent access unnoticed for extended periods.

Known aliases

Threat reports may refer to this family under multiple names:

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-KMCKernel Memory Integrity CheckingHardenT1014Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution.
D3-KPAKernel Patching & Privilege AuditingHardenT1068Enforce rapid OS kernel patch cycles and deploy Exploit Guard protections to block memory corruption and elevation exploits.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block 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_NTROOTKIT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Ntrootkit"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "ntrootkit" ascii wide nocase
        $s2 = "rootkit:win32/ntrootkit" ascii wide nocase
        $s3 = "win32/ntrootkit" ascii wide nocase
        $s4 = "rootkit.ntroot" ascii wide nocase
        $s5 = "ntroot kernel driver" ascii wide nocase
        $s6 = "trojan:win32/ntrootkit" 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 - Ntrootkit (Rootkit) Execution & Triage
id: 7256aedf-4ccb-5c7c-b792-65ca0d9db46a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Ntrootkit 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/ntrootkit
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.rootkit
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1014
- attack.t1068
- attack.t1543_003
- attack.t1562_001
- attack.t1057
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_NTROOTKIT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Ntrootkit 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 = "ntrootkit" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Immediately isolate the endpoint from the network; you cannot trust the operating system's reporting of network activity or running processes.
  2. Do NOT attempt to clean the machine using standard antivirus tools while the OS is running; the rootkit will simply hide from the scanner.
  3. Capture a full memory dump (RAM) for forensic analysis using a specialized tool that operates outside of the standard Windows API (if possible).
  4. Assume the endpoint is fundamentally untrustworthy; perform a bare-metal rebuild of the operating system after capturing forensic data.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not trust Task Manager, Process Explorer, or standard EDR alerts on the infected machine to provide an accurate picture of the threat.
  2. Avoid reconnecting the machine to the network before a full forensic investigation is complete; rootkits are often used to hide persistent backdoors.

References & External Analysis

Frequently Asked Questions

What is Rootkit:Win32/NTRootkit?

NTRootkit is a Windows kernel-level and user-mode rootkit designed to hide malicious processes, files, and network activity from detection tools.

How does NTRootkit hide processes from Task Manager?

It hooks NtQuerySystemInformation or uses DKOM to unlink active process blocks from the active process list in kernel memory.

How does NTRootkit achieve execution at the kernel level?

It loads a signed or exploit-vulnerable kernel driver (.sys) to execute code within Ring 0 privileged supervisor space.

Can standard antivirus programs detect an active NTRootkit?

Standard user-space tools are blinded; detection requires raw disk reading, kernel memory integrity analysis, or offline boot scanning.

What is the recommended remediation for kernel rootkits like NTRootkit?

Due to kernel-level tampering, recommended industry practice is taking forensic memory images followed by clean OS re-imaging.

How do I remove the Ntrootkit Rootkit from Windows?

Manual removal of Ntrootkit 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 Ntrootkit a virus or a Rootkit?

Ntrootkit is classified as a Rootkit. Unlike traditional viruses that infect files, modern malware like Ntrootkit typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Ntrootkit infection?

Symptoms of Ntrootkit 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 Rootkits

Want to prevent Ntrootkit and similar threats from compromising your organization? Read our comprehensive defensive guide: Rootkit & Bootkit Protection.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/ntrootkit.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.