DisclosureLens
GLOBALMalwareHealthcareHealthcareRansomwareInc RansomRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Health Sciences Centre

bd_9d4e68040c60cfa4 · schema v1 · pii pii-v2

Severity

High

Discovered

—

Filed

Oct 10, 2026

To disclose

—

Affected

Not disclosed

Confidence

50%

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: HealthcareDiscovered: 2026-10-11

Source: Ransomware.live

Post text · scraped from the leak site

The Health Sciences Centre in Winnipeg, one of the largest medical institutions, was targeted by us that resulted in the largest data breach among healthcare institutions. Our group chose not to completely disrupt the facility’s operations, recognizing the potentially devastating consequences that such an action could have had on patients’ lives and health. Nevertheless, Health Sciences Centre management stated that no sensitive data had been affected, despite having been informed otherwise. The data included, but was not limited to, the following information: Patient medical records: Full name, date of birth, address and phone number Hospital medical record number Diagnoses, medical history, allergies and medications Laboratory results, imaging reports Appointment dates, treatment details and physician information. Employee and healthcare professional information: Names, contact details, dates of birth and employee numbers Employment, payroll and banking information Professional credentials, work schedules and departmental assignments. Financial and insurance information: Billing records and payment histories Insurance or benefits claim information. Confidential hospital documents: Internal emails and staff communications System configurations, network diagrams and security procedures Database backups and exported spreadsheets. We would have very much preferred to avoid making this data breach public, but the management has left us with no other choice.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Oct 10, 2026

Claim posted

—

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

—

Compliance clock

Not assessable

Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.