Kido
Table of Contents
Overview
Worm:Win32/Kido (universally known in the cybersecurity community as **Conficker**) is one of the most infamous, widespread, and devastating computer worms in history. First detected in late 2008, it rapidly infected millions of Windows computers globally, including critical government, military, and corporate infrastructure. It is famous for its aggressive self-propagation mechanisms, its pioneering use of a Domain Generation Algorithm (DGA) for command-and-control, and its ability to completely disable Windows security services.
Understanding the Conficker (Kido) Worm
To an end-user, a Conficker infection might result in the inability to access security vendor websites (e.g., microsoft.com, symantec.com) and account lockouts. For a network administrator, Conficker is a nightmare; it causes massive network congestion due to its aggressive scanning and creates a highly resilient botnet capable of receiving arbitrary payloads from its masters. It proved how devastating a worm utilizing a known, unpatched vulnerability could be.
Execution and Unprecedented Spreading Mechanics
Conficker primarily spreads by exploiting **MS08-067**, a critical vulnerability in the Windows Server service (`T1210`). It actively scans the local subnet and the internet for unpatched machines, sending a crafted RPC request that triggers a buffer overflow, allowing it to execute code remotely and install itself without user interaction. It also spreads via USB drives using deceptive `autorun.inf` files (`T1091`) and attempts to brute-force network file shares using weak administrator passwords (`T1110.001`). Once installed, it drops itself as a randomly named DLL (e.g., `C:\Windows\System32\xxyyzz.dll`) and registers itself as a hidden Windows service (`svchost.exe`) (`T1543.003`). To prevent removal, it terminates AV processes, blocks access to security websites via DNS poisoning, and disables Windows AutoUpdate (`T1562.001`). Crucially, to receive updates and commands, later variants generated up to 50,000 pseudo-random domain names a day (DGA), making it incredibly difficult for authorities to sinkhole the C2 infrastructure (`T1568.002`).
Indicators of Compromise & Impact
The impact was the creation of the largest botnet in history at the time, and severe network disruption. Host-based IoCs include EDR alerts for anomalous DLLs loading into `svchost.exe` (specifically the `netsvcs` group), the inability to access Windows Update, and sudden Account Lockout events across the domain as the worm attempts lateral movement. Network IoCs include massive spikes in outbound port 445 (SMB) traffic (scanning) and thousands of DNS requests for non-existent, randomly generated domains.
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 |
|---|---|---|---|
T1210 | Exploitation of Remote Services (MS08-067 / SMB) | Lateral Movement | ATT&CK ↗ |
T1568.002 | Dynamic Resolution: Domain Generation Algorithms (DGA) | Command and Control | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools (Disabling AV and Windows Update) | Defense Evasion | ATT&CK ↗ |
T1091 | Replication Through Removable Media (USB autorun) | Lateral Movement | 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-RMC | Removable Media Access Control | Harden | T1091 | Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media. |
D3-NPS | Network Protocol Segmentation & Patching | Filter | T1210 | Disable legacy protocols (e.g. SMBv1) and restrict SMB/RPC lateral movement across internal subnet boundaries. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
D3-DNSR | DNS Reputation Analysis | Detect | T1568.002 | Deploy recursive DNS security resolvers with algorithmic domain scoring (entropy and n-gram models) to automatically sinkhole DGA queries. |
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_KIDO_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Kido"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "kido" 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 - Kido (Advanced Threat) Execution & Triage
id: bafc129b-26de-5921-88df-71946406929d
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Kido malware family. Detects proxy execution, reflective DLL loading, and
remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/kido
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1210
- attack.t1091
- attack.t1562_001
- attack.t1568_002
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_KIDO_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Kido 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 = "kido" 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 infected segments immediately; Conficker spreads autonomously at high speed via SMB over the local network.
- Ensure the MS08-067 patch (and all subsequent critical SMB patches) is applied universally across the enterprise.
- Implement strong Account Lockout policies and ensure local Administrator passwords are unique across all workstations (e.g., using Microsoft LAPS) to halt SMB brute-forcing.
- Use specialized Conficker removal tools, as the worm aggressively defends itself against manual removal and standard AV scans.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the network is clean until every single machine has been verified and patched; a single unpatched machine will re-infect the entire network.
- Avoid leaving default open file shares or weak passwords on network drives, as Conficker will rapidly exploit them to spread.
References & External Analysis
- Search "kido" on VirusTotal (External Analysis)
- Search "kido" on Any.Run (Sandbox Sandbox)
- Search "kido" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Kido and what threat category does it belong to?
Kido is classified as a Advanced Threat. 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 Kido establish persistence and evade defensive controls?
Kido 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 Kido compromise?
Security teams responding to Kido 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 lateral movement and credential access tactics does Kido leverage in enterprise intrusions?
Kido frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Kido maintain covert communications and evade perimeter network monitoring?
Kido often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove the Kido Advanced_Threat from Windows?
Manual removal of Kido 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 Kido a virus or a Advanced_Threat?
Kido is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Kido typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Kido infection?
Symptoms of Kido 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 Advanced_Threats
Want to prevent Kido 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/kido.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.