Skip to main content

Ransomware victim disclosure

All victims

Colla Health

Claimed by Direwolf · listed 2 days ago

2d
Age
since listed · data leaked

Status timeline

  1. ListedAug 15, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Listed on leak site
Aug 15, 2026

About the victim

AI dossier — public-source company profile

Colla Health is a US-based mental health services platform specializing in cancer-specific psychiatric and emotional support. They provide EMR-integrated mental health programs (including PHQ-2/PHQ-9 depression screening) to oncology clinics and cancer centers across the country, offering access to care within 48 hours and revenue-generating reimbursable services.

Industry
Healthcare Technology & Oncology Mental Health Services

Attack summary

Severity: critical — Confirmed exfiltration of large-scale regulated healthcare data (PHQ screening, full EHR records with 259k+ diagnoses, 176k+ demographics, 297k+ immunizations). Data includes protected health information (PII, dates of birth, medical record numbers, provider credentials, mental health diagnoses) from multiple oncology clinics across US jurisdictions (AR, OK). This falls under HIPAA-regulated data requiring breach notification. Mental health screening data combined with cancer diagnoses creates h

The direwolf group claims to have exfiltrated 24.6 GB of data comprising 332 files from Colla Health's oncology EHR registry and business databases. The breach includes patient medical records, mental health screening results, PHQ questionnaire data, clinical trial information, provider credentials, and administrative system access logs.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • EHR patient demographics (diagnoses, allergies, immunizations)
  • Mental health screening results (PHQ-2/PHQ-9 scores with dates)
  • Patient medical record numbers (MRN) and identifiers
  • Patient names, dates of birth, contact information
  • Provider credentials (NPI numbers, physician names)
  • Clinical visit records (oncology/chemotherapy/lab types)
  • Care plans, family history, immunization records
  • Patient appointment and booking data
  • Metabase application database (user logins, API keys, query logs)
  • Clinical trial numbers and protocols
  • Prospective patient and sales lead data (~108k prospects, ~5.5k leads)

What the group claims

Healthcare

The leak post

captured from the group's site
|  (US oncology-care data platform; OncoEMR/EHR registry + PHQ-2/PHQ-9 depression screening for multiple oncology clinics)  |  
| --- |  
| 24.6 GB, 332 files, , ~   |  
| EHR data registry (SQL Server source → Postgres snapshots)  |  
| --- |  
| Product DB: PHQ screening, patients, leads, appointments  |  
| Metabase app DB (query execution logs, users)  |  
### 3.1 Registry (EHR data registry; SQL Server source → Postgres snapshots)  
 |  
|  |  
 |  
| Named clinical values ("LastSupervisingMD", "Medication Reconciliation Complete")  |  
| Street / city / zip (AR / OK / US)  |  
| Patient documents assigned to staff  |  
| Clinical trial numbers, order set descriptions  |  
 |  
|  **MD / Chemo / Lab** visit types  |  
| Filler / placer order numbers, specimen / report dates  |  
|  (client IPs 10.11.x, insert / update counts)  |  
 |  
| Diagnoses / demographics / allergies  | 259,621 / 176,434 / 156,523  |  
| Immunizations / providers / protocols  | 297,796 / 343,540 / 294,765  | Immunization history, patient-provider links, default protocols  |  
| Family history, care plans, tasks, reminders, legacy production data (PHQ results 72,180, prospective patients 108,018, leads 5…

Sources

Source

Indexed 2 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 direwolf

Direwolf is a ransomware group that emerged in May 2025 with primarily financial motivations, having targeted 71 known victims across multiple sectors and geographic regions. The group's origin and potential affiliations remain undocumented in public threat intelligence reports, with no confirmed information regarding whether they operate as a Ransomware-as-a-Service model or as an independent entity. Their attack methodology and technical capabilities have not been extensively documented by major cybersecurity firms or government agencies, though their targeting patterns indicate a focus on manufacturing, technology, healthcare, and transportation/logistics sectors across Malaysia, the United States, Thailand, Singapore, and Taiwan. No major high-profile campaigns or significant ransomware demands have been publicly attributed to this group by CISA, FBI, or established security researchers such as Mandiant. Given the group's recent emergence and limited public documentation, their current operational status and long-term threat posture remain unclear, requiring continued monitoring by the cybersecurity community to establish a more comprehensive threat profile. The group has been linked to 96 public disclosures across our corpus. First observed on a leak site on May 27, 2025; most recent post August 17, 2026. The operation is currently active.

Also tracked as: DIRE WOLF.

Timeline of this disclosure

  • August 15, 2026Colla Health listed by direwolfon 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, Colla Health is reported in United States, a country with 3,162 ransomware disclosures in our corpus.

If your organisation is affected

A listing by direwolf means Colla Health 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, CISA (United States), as required for your jurisdiction.
  • Monitor for the data appearing on direwolf'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.