Nitol
Table of Contents
Overview
Nitol (cataloged across global cybersecurity threat intelligence as DDoS:Win32/Nitol, Trojan:Win32/Nitol, and Backdoor.Win32.Nitol) is a notorious Distributed Denial of Service (DDoS) botnet and backdoor trojan family analyzed by Microsoft Defender, Cisco Talos, and CISA. Prominently dismantled in part during Microsoft Digital Crimes Unit's operation against the 3322.org dynamic DNS infrastructure, Nitol was historically pre-installed onto counterfeit Windows operating system recovery disks and distributed via cracked software installers across East Asia and worldwide. Once active on an endpoint, Nitol establishes persistent TCP connections to attacker-controlled command-and-control servers, enabling operators to orchestrate coordinated high-volume SYN floods, UDP floods, and HTTP GET floods against corporate networks, government portals, and gaming servers. Nitol also includes keylogging modules, arbitrary file execution, and registry persistence hooks under HKLM\Software\Microsoft\Windows\CurrentVersion\Run.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Chinese_Ddos_Botnet_Framework
Known Derivatives & Downstream Variants: Nitol.A · Win32.Nitol.Gen · Ddos.Nitol
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 |
|---|---|---|---|
T1498.001 | Network Denial of Service: Direct Network Flood | Impact | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1056.001 | Input Capture: Keylogging | Collection | ATT&CK ↗ |
T1112 | Modify Registry | Defense Evasion | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols | Command and Control | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
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.
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
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-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-TR | Traffic Rate Limiting | Isolate | T1498.001 | Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks. |
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. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0c9d8e7f6a5b4b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0c9d8e7f6a5b4c3
Delivery vectors
Counterfeit Windows installation media and recovery ISOs pre-infected with Nitol stagersDrive-by compromise downloads delivering weaponized RTF documents exploiting CVE-2012-0158
Persistence mechanisms
HKLM\Software\Microsoft\Windows\CurrentVersion\Run\NitolBotServiceWindows Service registered via sc.exe create 'NitolSvc' binPath= '%System32%\nitol.exe'
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_NITOL_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Nitol"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "nitol" ascii wide nocase
$s2 = "ddos:win32/nitol" ascii wide nocase
$s3 = "trojan:win32/nitol" ascii wide nocase
$s4 = "backdoor.win32.nitol" ascii wide nocase
$s5 = "win32/nitol.bot" ascii wide nocase
$s6 = "nitol.ddos" 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 - Nitol (Ddos Bot) Execution & Triage
id: 3c46adda-f1b4-5595-bea6-a47c659c9813
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Nitol 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/nitol
- 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.ddos-bot
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1498_001
- attack.t1105
- attack.t1547_001
- attack.t1056_001
- attack.t1112
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_NITOL_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Nitol 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 = "nitol" 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 infected endpoint from the corporate network immediately to prevent participation in DDoS attacks.
- Block outbound connections to known Nitol dynamic DNS command-and-control domains at the perimeter firewall.
- Delete persistent registry run entries under HKLM\Software\Microsoft\Windows\CurrentVersion\Run and associated service binaries.
- Collect forensic artifacts and execute an enterprise antimalware sweep using Microsoft Defender or Cisco Talos solutions.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not allow endpoints to use unvetted dynamic DNS providers or direct outbound IRC/HTTP ports.
- Avoid deploying non-official Windows installation ISOs or recovery disks.
References & External Analysis
- CISA Alert TA12-340A - Microsoft Operation Against Nitol Botnet
- Microsoft Defender Threat Encyclopedia - DDoS:Win32/Nitol Analysis
- Cisco Talos Intelligence Group - Nitol Botnet Telemetry
- CISA Advisory: TA12-340A
- Search "nitol" on VirusTotal (External Analysis)
- Search "nitol" on Any.Run (Sandbox Sandbox)
- Search "nitol" on MalwareBazaar (Malware Samples)
North American Authority Advisory (CISA / NIST)
The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: TA12-340A ↗
Frequently Asked Questions
What is the Nitol botnet?
Nitol is a widespread DDoS botnet and backdoor trojan family analyzed by Microsoft Defender, Cisco Talos, and CISA.
How was Nitol historically distributed?
It was notoriously distributed pre-installed on counterfeit Windows installation media and bundled within pirated software activators.
What DDoS attack vectors does Nitol support?
Nitol supports SYN flood, UDP flood, ICMP flood, and HTTP GET request flooding against remote IP targets.
Which CVE vulnerabilities have been exploited by Nitol distribution campaigns?
Threat actors delivering Nitol have historically exploited document vulnerabilities including CVE-2012-0158 and CVE-2014-6332.
How can incident responders eradicate Nitol from compromised hosts?
Isolate the endpoint, block outbound C2 dynamic DNS domains, remove startup registry keys, and run an enterprise antimalware scan.
How do I remove the Nitol Ddos_Bot from Windows?
Manual removal of Nitol 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 Nitol a virus or a Ddos_Bot?
Nitol is classified as a Ddos_Bot. Unlike traditional viruses that infect files, modern malware like Nitol typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Nitol infection?
Symptoms of Nitol 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 Ddos_Bots
Want to prevent Nitol and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 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/nitol.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.