TECH / Windows 5 min read

Net-Worm.Win32.Kido (Conficker) – Symptoms and Step-by-Step Removal

Antonio NEMCD Author
Published Jan 30, 2009 · 5 min

Today I ran into the network worm Net-Worm.Win32.Kido (also known as Conficker, Downadup, and Win32.HLLW.Shadow.based). On one of our servers, the Netlogon and Server services suddenly stopped, cutting off access to shared folders – something that had never happened before. I restarted the services and things came back up, but it was obvious something was off, so I started digging for the culprit.

Net-Worm.Win32.Kido and Windows protection against the network wormNet-Worm.Win32.Kido (Conficker) targets unpatched Windows vulnerabilities

Kido affects Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and newer builds, using a polymorphic packer that constantly changes its file signature and makes standard detection harder.

How to Spot a Kido Infection on a System and Network

Besides crashed networking services and inaccessible shared folders, the worm leaves several clear traces:

  • Blocked security sites: an infected machine refuses to open Microsoft, Kaspersky, Dr.Web, and other antivirus vendor websites.
  • Network spike: LAN traffic jumps as the worm scans TCP ports 445 and 139 via the MS08-067 vulnerability (firewalls log Intrusion.Win.NETAPI.buffer-overflow.exploit).
  • Files and services: a DLL with a random Latin name (such as sfefs.dll) appears in C:\Windows\system32\ along with a matching service, while autorun.inf and RECYCLED\{SID}\random_name.vmx are written to USB drives and writable network shares.
  • Domain networks: in Active Directory domains, clean domain controllers and machines used by Domain Admins first – otherwise the network gets reinfected after reboot.

Step-by-Step Removal and Security Patches

To clean the worm permanently and avoid immediate reinfection, follow this exact order:

  1. Disconnect the network: physically unplug the infected PC or server from the LAN and internet (reconnect only after every machine in the network is clean).
  2. Run a removal tool: run KidoKiller with Administrator rights (under a standard user account it crashes after 5–10 seconds) or Dr.Web CureIt! downloaded on a clean PC.
  3. Install Microsoft patches: close vulnerabilities MS08-067, MS08-068, and MS09-001.
  4. Re-scan after reboot: restart the machine, run KidoKiller or an antivirus scan again, disable AutoRun on removable media, and replace weak passwords.

Local Mirror of Removal Tools and Patches

Because Kido blocks downloads directly from Microsoft and antivirus vendor sites, here are local mirrors of the required tools and updates:

On Windows 2000 SP4, also check security bulletin MS08-065 (XP SP2/SP3 and Server 2003 SP1/SP2 are not affected). BitDefender (including QuickScan) and Dr.Web (CureIt!) also offer dedicated Downadup/Conficker cleaners.

KidoKiller (KK.exe) Command-Line Switches

For a thorough scan from Command Prompt inside the utility folder, run:

kk -j -t -a -r -f

Full switch reference (run kk --help for more):

Switch Description
-p <path> Scan a specific directory
-f Scan fixed and removable hard drives
-n Scan network drives
-r Scan USB flash drives
-y Exit without waiting for a keypress
-s Silent mode without a console window
-l <file> Write scan log to a file (add -v for verbose logging)
-z Restore BITS, wuauserv, and ERSvc/WerSvc services
-x Restore visibility of hidden and system files
-a Disable AutoRun across all drives
-m Monitor threads, scheduled tasks, and services
-j Restore the SafeBoot registry key so Safe Mode works again

Starting with version 3.4.6, KK.exe returns an %errorlevel% exit code: 3 – active worm threads removed, 2 – inactive files removed, 1 – malicious scheduled tasks or hooks found (the host is clean, but other machines on the LAN may be infected), 0 – clean.

Removing Leftover RECYCLER Folders on Network Shares

After cleaning, network shares often keep a RECYCLER folder with a locked file like jwgkvsq.vmx that refuses deletion even under Administrator. Open the folder in FreeCommander or Total Commander (avoid Windows Explorer), take ownership as Administrator, grant Full Control, and remove the directory from Command Prompt:

rmdir /s /q "./S-5-3-~1"
rmdir /s /q RECYCLER

In my own network, running KidoKiller, patching all servers and workstations, and double-checking with Dr.Web CureIt! cleared the infection completely and stopped the crashes.

Related posts:

Leave a Comment