JETPLAIN / HISTORICAL RESEARCHACCESSION HIST-007

THE HISTORIC HACK FILES

Conficker: one family name, several different problems

PERIOD2008–2010; multiple variants

EDITIONShort field file

AUTHOR REVIEW2026-11-20

An independently written Jetplain dossier · not a government document

The short version

Conficker was a Windows worm family with multiple variants. Understanding the family means keeping two questions separate: how a particular version spread, and how responders tried to interrupt its communications.

One name does not mean one route

Microsoft’s Conficker.B description identifies network spread, weak-password opportunities, and removable drives. It also describes interference with security services. Those findings concern that variant; they should not be copied backward onto every earlier sample.

The patch addressed a specific opening

Microsoft published MS08-067 on October 23, 2008. It addressed a Server service flaw involving specially crafted RPC requests. The bulletin identified unauthenticated remote code execution on affected Windows 2000, XP, and Server 2003 systems. That is a particular exposure, not an explanation of every Conficker infection.

Why domain registries joined the response

ICANN’s 2010 review describes coordination among researchers, vendors, ICANN, registries, and registrars to prevent the malware’s operators from using generated domain names. The response targeted communications as well as infected computers.

The report explicitly says containment did not eradicate the worm or completely dismantle the botnet. Disrupting an instruction channel and cleaning an infected machine are different outcomes.

From the workbench

Before calling a response successful, name what it achieved. Was a route blocked, a machine cleaned, or an exposure repaired? Each answer needs its own evidence. That is an analytical takeaway, not a present-day removal guide.

What this file leaves open

This short account omits an exact infection total, author identification, and a complete variant chronology. Microsoft supplies the technical descriptions; ICANN supplies a participating institution’s response account. Three source documents do not mean three independent investigators.

Source register

Browse Historic Hacks