Cyber Incident Victim: Ontario Progressive Conservative Party
Date:
Nov 2017
Location:
Canada
Summary
The Ontario Progressive Conservative Party experienced a ransomware attack compromising its internal database containing personal details of over one million voters, supporters, donors, and volunteers. An external vendor restored the system from backups and confirmed no data exfiltration occurred during the incident.
| CIA Posture | Motives | Tactics, Techniques & Procedures |
|---|---|---|
| Available to members | 3 motives | 1 technique |
| Threat Actors | Type | Location |
|---|---|---|
| 0 actors | Available to members | Available to members |
Description
In early November 2017, the Ontario Progressive Conservative Party experienced a ransomware attack that compromised its internal voter database. The attackers encrypted the database, rendering it inaccessible to party personnel. This database contained extensive personal information, including names, phone numbers, and other details belonging to over one million individuals comprising eligible Ontario voters, party supporters, financial donors, and campaign volunteers. The compromised system was managed by an external third-party vendor responsible for hosting and maintaining the servers. Following the attack, the vendor initiated recovery procedures using backup systems, successfully restoring the database without paying the ransom. The vendor subsequently asserted no evidence indicated data exfiltration or theft during the incident. The party did not publicly disclose the breach until January 2018, when media reports by CP24 brought the incident to light.

The incident exposed sensitive personal information tied to political engagement activities across Ontario. While the ransomware’s primary mechanism involved data encryption rather than confirmed theft, the database’s contents represented a high-value target containing voter affiliations and donor histories. The external vendor’s restoration from backups constituted the primary technical response, suggesting existing disaster recovery protocols mitigated prolonged operational disruption. No public statements from the party detailed specific security improvements or forensic investigations undertaken post-incident. The delayed disclosure timeline—approximately two months between the attack and its public acknowledgment—raised questions about incident reporting transparency, though the party did not elaborate on reasons for the gap. The vendor maintained confidence in the integrity of restored data and reiterated no stolen information required secondary containment measures.
