Date
August 16, 2005
Location
United States
Industry
Manufacturing
Access vector
Unknown
OT targeting
Indirect: IT dependency
Primary peril
None
Impact duration
Up to 50 minutes

DaimlerChrysler Zotob worm plant shutdowns, 2005

DeNexusIncident analysis
Cover image for the incident analysis: DaimlerChrysler Zotob worm plant shutdowns, 2005

The incident path, stage by stage

Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.

Scroll sideways to see every stage.

    IT stagesOT stagesConfirmedPerilReportedImpliedUnknownNot in pathLink not established DeNexus analysis of public sources, as of October 22, 2026
    On this page

      Highlights

        What happened. On August 16, 2005, the Zotob worm and related worms infected unpatched Windows 2000 machines in DaimlerChrysler’s US manufacturing operations, and 13 assembly plants in six states went offline[1]. A company spokesperson said the plants were down “for almost an hour”, “stranding some 50,000 auto workers”[1][2].

        Why it matters. An indiscriminate internet worm with no industrial capability stopped car production, because the Windows machines production depended on were in the same unpatched population as everyone else’s[2][1]. The cost figure most often attached to the incident is not in the source it is attributed to.

        About this analysis. This analysis sets out what is known, stage by stage. It rests mainly on one contemporaneous press report and a government report that repeats it, and it reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.

        Highlights

        • Thirteen DaimlerChrysler plants in Illinois, Indiana, Wisconsin, Ohio, Delaware and Michigan stopped for between five and 50 minutes while infected Windows systems were patched[1][2].
        • Microsoft had issued the patch for the Plug and Play flaw the worm exploited on August 9, 2005, seven days before the plants stopped[3].
        • The worm was not aimed at DaimlerChrysler: the FBI says it disrupted more than 100 US companies, including major news organizations. Two men were arrested on August 25, 2005[4].
        • No loss figure has been disclosed. A $14 million estimate in circulation is attributed to a 2007 GAO report that contains no dollar figure for the incident[2].

        Attack flow

        • Updated: 2026-10-22
        • Intent: Malicious [confirmed | indiscriminate worm, not aimed at DaimlerChrysler]
        • Threat actors: Cyber Criminals [confirmed | arrests announced by the FBI]
        • Access vector: Not established [unknown | Entry into the network not stated]
        • IT impact: Malware [confirmed | Zotob, T1210]; System Outage [confirmed | PC outages]
        • OT targeting: Indirect: IT Dependency [confirmed]
        • OT sophistication: Not applicable [not in path | Generic Windows worm, no OT capability]
        • OT impact: Not established [unknown | No controller described as affected]
        • Perils: No Perils [confirmed | Lines stopped and restarted]
        • Financial losses: Business Interruption [confirmed]; Cyber Incident Response [confirmed]

        What happened

        Microsoft issued bulletin MS05-039 on August 9, 2005, for a flaw in the Windows Plug and Play service. It rated the flaw Critical for Windows 2000 and said an anonymous attacker could exploit it remotely over TCP ports 139 and 445[3]. Public exploit code was posted by August 12[5], and the FBI puts the worm’s release 12 days before the August 25 arrests[4]. Zotob and other worms of the same week all used the exploit[1].

        On Tuesday, August 16, at around 3:00 p.m., the worms hit DaimlerChrysler. Thirteen US assembly plants went offline. Spokesperson Dave Elshoff said vehicle production stopped “for up to 50 minutes”, while staff patched Windows systems “that are integral to the manufacturing process”; eWeek reported that the outages “ranged from 5 to 50 minutes, but no workers were sent home”[1]. Elshoff said a shift change that normally happens at 3:00 p.m. reduced the impact, that the worms also caused PC outages at the company’s financial services group, and that he “wouldn’t characterize our operations as out of the woods yet”[1].

        In 2007, the US Government Accountability Office (GAO) included the case in a report on control systems: “a round of Internet worm infections knocked 13 of Daimler Chrysler’s U.S. automobile manufacturing plants offline for almost an hour”, “leaving workers idle as infected Microsoft Windows systems were patched”[2]. eWeek named CNN, ABC, The New York Times and SBC Communications among the worm’s other victims, and GAO named Caterpillar[1][2].

        Intent: malicious, but not aimed here

        Zotob was written and released deliberately, so the path starts at Malicious. But it had no target list and no operator choosing victims. It reached whatever was unpatched and exposing the Plug and Play service[3][1]. The FBI says it disrupted more than 100 US companies[4]. The loss at DaimlerChrysler was real, and the attacker had no particular interest in causing it.

        Threat actors: arrested worm authors

        The FBI announced two arrests on August 26, 2005: Farid Essebar, 18, a Moroccan national born in Russia, and Atilla Ekici, 21, a resident of Turkey[6]. The FBI later said they were arrested on August 25, 12 days after the worm was released, and that a Moroccan court sentenced Essebar to two years in prison and a second man to one year[4]. No sentence for Ekici is reported, and no source ties any charge to DaimlerChrysler specifically.

        Access vector: not established

        How the worm first got into DaimlerChrysler’s network is not stated by the company, GAO or the press. No source mentions an infected laptop, a phishing lure or any human-operated intrusion. What is known is how it spread once inside: the worms used the Plug and Play exploit to move from machine to machine, which MITRE calls Exploitation of Remote Services[1][7]. The company said its network was probably hit by more than one worm[1].

        IT impact: infected Windows machines

        The worms infected Windows 2000 machines across the company’s US manufacturing operations, and also caused PC outages at its financial services group[1]. Recovery was patching: staff patched the affected Windows systems while the lines stood still[1][2]. No source describes data being destroyed, encrypted or stolen.

        OT targeting: an IT dependency

        Production stopped because machines that production depended on were infected. GAO places the infection on Windows hosts, and the company described them as “integral to the manufacturing process”[2][1]. Whether those hosts were plant-floor terminals inside the manufacturing network, or corporate machines whose loss stopped the line indirectly, is not established. No source describes a PLC, robot or line controller as affected. That makes this an indirect OT impact through an IT dependency.

        No OT-specific control would have done more here than a patched Windows estate.

        OT sophistication: not applicable

        Zotob exploited a generic Windows service. Nothing in it speaks an industrial protocol, understands a process, or tells a car plant from a newsroom, which is why it hit news organizations in the same week[1]. There is no OT capability to classify, so this stage is marked Not applicable.

        OT impact: not established

        The lines stopped, which MITRE’s Loss of Productivity and Revenue technique describes as loss of production caused indirectly by an attack[8]. That is a production effect, not an effect on control systems. No source describes a loss of view or control, or any manipulation, on plant-floor equipment, and the boundary between the infected machines and the process is not documented.

        Perils: no physical event

        No source reports damage to equipment or product, a fire, a release or an injury. The assembly lines stopped for up to 50 minutes and restarted[1]. Nothing in the confirmed facts implies a physical peril.

        Financial losses: what it cost

        DaimlerChrysler disclosed no loss figure, then or later. The production halt and the emergency patching are confirmed; their cost is not[1][2].

        Loss evidence

        • Confirmed: Lost revenue and productivity (13 plants stopped, some 50,000 workers idled); Network event response and recovery (emergency patching of Windows systems)
        • Implied: Voluntary improvements
        • Not supported: Manual operations and workarounds

        A 2015 scenario report by the Cambridge Centre for Risk Studies and Lloyd’s lists the incident with “An estimated $14m in downtime costs”, citing a 2007 GAO report. GAO-07-1036 describes the incident in one sentence and contains no dollar figure for it[2], and no other source reviewed carries the $14 million. This analysis treats it as unsourced. The only published cost figure for Zotob is an average of $97,000 and 80 hours of cleanup per affected company, an average across victims that is not DaimlerChrysler’s number[9].

        What this incident shows

        The defining fact is timing. Microsoft issued a critical patch on August 9, public exploit code followed by August 12, the worm by August 13, and DaimlerChrysler’s Windows 2000 machines were still unpatched on August 16, when they were patched while the lines stood still[3][5][4][1]. The gap was patch latency in the Windows population around the plants, not anything specific to their control equipment.

        The case also shows how a loss figure can harden without a source. A thirteen-plant halt that idled about 50,000 workers produced no disclosed cost, and the number most often repeated is not in the report it cites[2]. For anyone assessing this kind of risk, the documented facts are the plants, the workers and the minutes; the dollars are not on the record.

        References

        1. Roberts, Paul F. “Zotob, PnP Worms Slam 13 DaimlerChrysler Plants.” eWeek, 18 Aug. 2005. eweek.com/security/zotob-pnp-worms-slam-13-daimlerchrysler-plants/
        2. U.S. Government Accountability Office. “Critical Infrastructure Protection: Multiple Efforts to Secure Control Systems Are Under Way, but Challenges Remain.” GAO-07-1036, Sept. 2007. govinfo.gov/content/pkg/GAOREPORTS-GAO-07-1036/html/GAOREPORTS-GAO-07-1036.htm
        3. Microsoft. “Microsoft Security Bulletin MS05-039: Vulnerability in Plug and Play Could Allow Remote Code Execution and Elevation of Privilege (899588).” Microsoft Learn, 9 Aug. 2005. learn.microsoft.com/en-us/security-updates/securitybulletins/2005/ms05-039
        4. Federal Bureau of Investigation. “Moroccan Authorities Sentence Two in Zotob Computer Worm Attack.” Press release, 13 Sept. 2006. fbi.gov/news/pressrel/press-releases/moroccan-authorities-sentence-two-in-zotob-computer-worm-attack
        5. houseofdabus. “Microsoft Windows Plug-and-Play Service - Remote Universal (MS05-039).” Exploit Database 1149, 12 Aug. 2005. exploit-db.com/exploits/1149
        6. Federal Bureau of Investigation. “FBI Announces Two Arrests in Mytob and Zotob Computer Worm Investigation.” Press release, 26 Aug. 2005. fbi.gov/news/pressrel/press-releases/fbi-announces-two-arrests-in-mytob-and-zotob-computer-worm-investigation
        7. MITRE. “Exploitation of Remote Services, Technique T1210 - Enterprise.” MITRE ATT&CK (checked 22 Oct. 2026). attack.mitre.org/techniques/T1210/
        8. MITRE. “Loss of Productivity and Revenue, Technique T0828 - ICS.” MITRE ATT&CK for ICS (checked 22 Oct. 2026). attack.mitre.org/techniques/T0828/
        9. ICS STRIVE. “Zotob Worm.” icsstrive.com/malware/zotob-worm/