Date
June 6, 2017
Location
Australia
Industry
Government
Access vector
Removable Media
OT targeting
Direct
Primary peril
None
Impact duration
16 days

Victoria road safety camera WannaCry infection, 2017

DeNexusIncident analysis
Cover image for the incident analysis: Victoria road safety camera WannaCry infection, 2017

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. From June 6, 2017, the WannaCry malware spread through Victoria’s fixed road safety camera network, infecting 43 Redflex camera control units and 67 Jenoptik site controllers, all running Windows 7[1]. Victoria Police cancelled 590 fines and withdrew or held back thousands more while the integrity of the cameras was in doubt[2][3]. The Road Safety Camera Commissioner found that the malware’s encryption had failed and that the devices that measure speed were unaffected[1].

        Why it matters. Malware ran on 110 field controllers of a state enforcement system but could not reach the measurement every fine depends on, because the speed-measuring devices sat outside the infected computers[1]. How the malware got in was never established[4].

        About this analysis. This analysis sets out what is known, stage by stage. It rests mainly on the Commissioner’s two reports, which correct the 2017 press account of how the malware arrived. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.

        Highlights

        • The Commissioner’s interim report counted 110 infected Windows 7 controllers; the network had 280 cameras, and its Linux-based camera and detection systems were unaffected[1][3].
        • The state’s Department of Justice and Regulation blamed a contractor, and the press reported a USB stick. The Commissioner found the variant could not spread by USB and could not identify the source[4].
        • Police cancelled 590 fines on June 23, then put the affected tickets at 7,500 to 8,000. After the interim report found no effect on integrity, 3AW reported that the fines would stand[2][3][5].
        • The impact outlasted the infection: a freeze in testing and certification let site certifications lapse, and recovery was still incomplete at the end of December 2017[4].

        Attack flow

        • Updated: 2026-10-22
        • Intent: Malicious [confirmed | Victoria collateral]
        • Threat actors: Nation-State [confirmed | Lazarus Group, WannaCry]
        • Access vector: Removable Media [reported | T0847, rejected by the Commissioner]; Supply Chain [reported | T0864, tester’s file, per the Department]
        • IT impact: Malware [confirmed | WannaCry, encryption failed]
        • OT targeting: Direct OT Compromise [confirmed | Roadside controllers]
        • OT sophistication: Not applicable [not in path | Commodity malware]
        • OT impact: None [not in path | Measurement unaffected]
        • Perils: No Perils [confirmed | Administrative harm only]
        • Financial losses: Business Interruption [confirmed]; Cyber Incident Response [confirmed]

        What happened

        The first known infection in Victoria’s camera network came on June 6, 2017, more than three weeks after the global WannaCry outbreak of May 12, on cameras that were not connected to the internet[4][3]. From that day, older Windows XP and 2000 systems began to experience increased downtime. A vendor suspected a virus on June 14 and formally notified the Department on June 15, and one vendor’s sites were deactivated from June 14, producing no infringements until June 21[4].

        The public learned of it on June 22, when the radio station 3AW reported dozens of infected cameras[6]. The Commissioner’s final report records that the Police Minister, Lisa Neville, and the Commissioner’s own office were both first told by the media[4]. By June 22 all infected systems had been patched[1]. On June 23, Victoria Police cancelled 590 fines. Acting Deputy Commissioner Ross Guenther said: “I cancelled the fines because I think it’s important the public has 100 per cent confidence in the system”[2]. On June 24, Assistant Commissioner Doug Fryer put the affected tickets at 7,500 to 8,000, about 1,643 withdrawn and about 5,500 embargoed[3]. The press count of infected cameras rose from about 55 to at least 97[2][7].

        The Commissioner’s interim report of July 6 found that the encryption component “failed to deploy”, that the devices which measure and record speed were external to the infected computers, and that there was no reason to keep the infringements withheld[1]. On July 7, 3AW reported that the fines would stand[5]. The final report, dated May 3, 2018, found that the source of the infection could not be identified[4]. On May 24, 2018, the Victorian Government accepted all of the Commissioner’s recommendations[8].

        Intent: malicious software, no target

        WannaCry is ransomware, built and released deliberately, so the path starts at Malicious. Its arrival in Victoria was not aimed at anyone. The first infection came more than three weeks after the global outbreak[4], and the Commissioner found no evidence of any malicious intent in how it reached the camera network[4]. The intent is recorded as malicious because the software was; nothing suggests that anyone set out to disable Victoria’s cameras.

        Threat actors: the authors of WannaCry

        WannaCry was attributed to the Lazarus Group, and to North Korea, by the United States and allied governments in December 2017. It is shown on the map as Nation-State. Victoria was collateral damage from residual WannaCry, a late reinfection rather than a chosen target[4].

        No person or company has been identified as having brought the malware into the camera network. The final report notes that no organization volunteered itself as a possible source of the infection[4].

        Access vector: never established

        In June 2017, the Department said the virus was “mistakenly introduced by a contractor”[2], and the press reported that a maintenance worker had plugged in a USB stick on June 6[3][6]. The Commissioner rejected that route. Accepting expert advice, his final report says the variant “only attempts to propagate via a Windows File Sharing (SMB) flaw”, and that there is “no indication that the malware could propagate by infecting a portable USB drive”[4]. On July 7, 2017, he told 3AW: “I’m told there were no USB sticks involved”[9].

        The Department also said the infection came through an infected file of one of the testers. The report confirms that a contractor’s test laptop, without up-to-date virus templates, was infected and went undetected for at least nine days, but it does not find that the laptop was the source: “It has not been possible to identify the source of the infection”[4]. Both routes are shown as reported, and neither is established.

        IT impact: malware that could not encrypt

        The malware ran, but its payload did not. The Commissioner found that the encryption component “failed to deploy”, with no evidence of encryption on any system[1], and the final report says the variant “was incapable of encrypting data”[4]. It spread over the Windows SMB flaw addressed by the MS17-010 patch: more than 100 infected hosts were trying to spread it, and the 102 systems with log data were all infected within 48 hours[4][10]. Infected units were patched by June 22[1]. The report flags test and maintenance equipment moving between the corporate and camera networks as “a threat to both”[4].

        OT targeting: a direct compromise

        The infected devices were the roadside controllers themselves, 43 Redflex camera control units and 67 Jenoptik site controllers, not a back-office estate that the cameras depended on[1]. That makes this a direct OT compromise. The classification records what was compromised, not what anyone intended: WannaCry was not written with speed cameras in mind, and its arrival here was not targeted[4].

        OT sophistication: not applicable

        This was commodity ransomware, arriving by a route nobody established, whose own encryption payload failed to run[1][4]. It used no knowledge of camera systems and no OT-specific technique. On the Windows 7 controllers it spread without visible effect: the report says “the performance impact on infected machines was negligible”[4]. The stage is marked Not applicable on the map.

        OT impact: availability lost, measurement intact

        No measurement, control or physical process was affected. The devices that measure and record speed are external to the infected computers and were unaffected, and the Commissioner found “no evidence that the WannaCry infection has affected the integrity of Speed and Red-Light camera infringements”[1].

        Availability did suffer. Older Windows XP and 2000 machines “failed (crashed) within minutes of coming under attack”, and one vendor’s sites were deactivated and produced no infringements from June 14 to 21[4]. In MITRE ATT&CK for ICS terms that is Loss of Availability, an outage rather than a loss of control or view, so the map shows no OT impact. The Commissioner noted that a more malignant virus “would likely have been detected almost immediately”[4].

        Perils: no physical event

        The harm was administrative: fines were withheld and camera sites were taken offline. Both Commissioner reports find no effect on measurement, data or hardware[1][4], and no source reports damage, fire, injury or any other physical loss.

        The malware reached the controllers, but the measurement every fine depends on was out of its reach.

        Financial losses: no published cost

        No cost figure for the incident was published by the Department, Victoria Police, the Commissioner or the camera operators, and the final report contains none[4]. One figure circulates: 3AW reported in May 2018 that the virus could cost the budget A$18.7 million in lost revenue, and Neville, asked on air about “about $20 million”, said “It is in that range. It is ugly”[11]. It was never published as a government figure, and it is forgone enforcement revenue, an opportunity cost to the state rather than a loss, so it is not carried in the ledger.

        Loss evidence

        • Confirmed: Lost revenue and productivity (enforcement suspended; 590 fines cancelled and 7,500 to 8,000 withdrawn or embargoed); Network event response and recovery; Legally mandated improvements (all recommendations accepted)
        • Not supported: Production data integrity; Embedded device replacement

        The impact ran past the infection. No testing, certification or maintenance took place between June 28 and July 20, 2017, site certifications lapsed, and “as at the end of December 2017 there was still incomplete recovery”[4]. Press reports of about 55,000 suspended infringements[12] are not reconciled with the police figure of 7,500 to 8,000 by any document.

        What this incident shows

        This is a clear example of a consequence boundary working. Malware executed on 110 field controllers, and the measurement on which every infringement depends was never reachable, because the speed-measuring devices were separate from the controllers that were infected[1]. That separation was almost certainly an engineering choice for measurement and evidentiary reasons rather than a security design, but it bounded the consequence of a successful compromise.

        The gaps were organizational. The Commissioner found the cameras were infected “due to insufficient security measures and an inadequate adherence to set practices”, and that no organization volunteered itself as a possible source, perhaps because of “the risk of a fine for breach of contractual service delivery standards”, an approach that in his view “discourages early reporting”[4]. AAP reported that the contractors were slow to notify the Department[13], and the Minister learned of a sixteen-day infection from a journalist[4].

        References

        1. Road Safety Camera Commissioner (Victoria). “Interim Report on Viral Infection of the Fixed Digital Road Safety Camera System.” 6 July 2017. cameracommissioner.vic.gov.au/file-download/download/public/94
        2. Mannix, Liam, and Melissa Cunningham. “Police cancel fines from Bendigo cameras.” The Age, as carried by Bendigo Advertiser, 23 June 2017. bendigoadvertiser.com.au/story/4749043/police-cancel-fines-from-bendigo-cameras/
        3. Vomiero, Jessica. “Traffic tickets withdrawn in Australia after cameras hit by WannaCry virus.” Global News, 24 June 2017. globalnews.ca/news/3553543/camera-traffic-tickets-withdrawn-australia-wannacry-virus
        4. Road Safety Camera Commissioner (Victoria), John Voyage. “Report to the Minister for Police on the Malware Infection to the Fixed Digital Road Safety Camera System.” 3 May 2018. cameracommissioner.vic.gov.au/file-download/download/public/90
        5. 3AW. “EXCLUSIVE: Fines from infected cameras set to stand.” 7 July 2017. 3aw.com.au/?p=20934
        6. 3AW. “EXCLUSIVE: Dozens of traffic cameras infected with virus.” 22 June 2017. 3aw.com.au/?p=20081
        7. “Victorian traffic cameras infected with WannaCry.” Technology Decisions, 26 June 2017. technologydecisions.com.au/content/security/article/victorian-traffic-cameras-infected-with-wannacry-1255044046
        8. Premier of Victoria. “Strengthening Victoria’s Road Safety Camera Network.” Media release, 24 May 2018. premier.vic.gov.au/strengthening-victorias-road-safety-camera-network
        9. 3AW. “‘We may never know why’: Camera commissioner.” 7 July 2017. 3aw.com.au/?p=20941
        10. MITRE. “Exploitation of Remote Services, Technique T0866 - ICS.” MITRE ATT&CK for ICS, read 22 Oct. 2026. attack.mitre.org/techniques/T0866/
        11. 3AW. “Neil Mitchell details blowout and failures in speed camera network after cyber virus.” 24 May 2018. 3aw.com.au/?p=37486
        12. “Fines issued despite camera virus.” Webbikeworld, 7 July 2017. webbikeworld.com/fines-issued-despite-camera-virus/
        13. Talbot, Christopher (AAP). “Victoria speed camera virus fines.” The New Daily, 25 June 2017. thenewdaily.com.au/news/state/vic/2017/06/25/victoria-speed-camera-virus-fines