Skip to main content

Ransomware victim disclosure

All victims

Canadian Mental Health Association

Claimed by Storm · listed 4 days ago

3d
Age
since listed · data leaked

Status timeline

  1. ListedAug 14, 2026
  2. Data leakeddate unknown

At a glance

Group
Storm
Status
Data leaked
Country
Canada
Listed on leak site
Aug 14, 2026

About the victim

AI dossier — public-source company profile

The Canadian Mental Health Association is a national mental health charity providing advocacy, education, research, and support services to persons experiencing mental illness across Canada. Headquartered in Toronto and Ottawa, CMHA operates a federated network of provincial divisions and regional branches delivering peer support, crisis intervention, workplace mental health programs, and recovery services.

Industry
Mental Health Services & Advocacy
Address
595 Montreal Road, Suite 303, Ottawa, ON K1K 4L2 Canada; 250 Dundas Street West, Suite 401, Toronto, ON M5T 2Z5 Canada
Employees
5000-10000

Attack summary

Severity: high — Confirmed exfiltration of data from a healthcare organization handling sensitive mental health records and personal information of vulnerable populations, with disclosed status indicating data has been published. Healthcare data breaches involving mental health records are regulated and highly sensitive.

Storm claims to have exfiltrated data from the Canadian Mental Health Association. The specific data types and operational impact are not detailed in the leak post.

high

What the group claims

The Canadian Mental Health Association provides mental health services and support. The Association offers advocacy, education, research, and services to persons experiencing mental illness throughout Canada and is headquartered in Toronto, Ontario. The company headquarters is located in 595 Montreal Road, Suite 303, Ottawa, ON K1K 4L2 Canada and 250 Dundas Street West, Suite 401, Toronto, ON, M5T 2Z5 Canada. 5K - 10K Employees

Sources

Source

Indexed 4 days ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Storm

Storm is a ransomware group first observed in August 2026, operating with an apparent financial motivation based on its targeting profile, though limited public documentation exists given its recent emergence and relatively small victim footprint. The group has claimed or been attributed to attacks against at least six known victims, with the United States representing its primary target geography. Storm has demonstrated a preference for targeting the healthcare and manufacturing sectors, alongside a broader category of other industries, suggesting an opportunistic rather than highly specialized targeting philosophy. Due to the group's recent emergence and limited victim count, comprehensive technical details regarding its initial access vectors, encryption methodology, tooling, or affiliation with known threat actor ecosystems have not yet been formally documented by CISA, the FBI, Mandiant, or other major threat intelligence publishers as of the time of this writing. No confirmed RaaS infrastructure, dark web leak site activity, or law enforcement actions against the group have been publicly attributed or reported in open sources. Given its nascent operational timeline beginning in 2026, Storm should be monitored as an emerging threat, particularly within the healthcare sector where ransomware attacks carry significant operational and patient safety implications, but analysts should treat any further characterization beyond the known victim and targeting data with caution pending additional corroborating intelligence. The group has been linked to 19 public disclosures across our corpus. First observed on a leak site on August 7, 2026; most recent post August 14, 2026. The operation is currently active.

Timeline of this disclosure

  • August 14, 2026Canadian Mental Health Association listed by Stormon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Healthcare sector, which has 2,608 disclosures indexed across all operators we track. Geographically, Canadian Mental Health Association is reported in Canada, a country with 319 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Storm means Canadian Mental Health Association appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, CCCS (Canada), as required for your jurisdiction.
  • Monitor for the data appearing on Storm's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.