UnknownHealthcareHealthcareCustomer Data InvolvedIdentity (basic)PHILowContained

Dameron Hospital

bd_59ac0f3e06125672 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Apr 2, 2025

To disclose

—

Affected

Not disclosed

Linked

9 records

Confidence

66%

Full breach record for Dameron Hospital →2 incidents on file

Dameron Hospital reported a data security incident where unauthorized access or acquisition of personal information occurred between November 4 and November 5, 2023. The affected data includes full names and potentially protected health information. The hospital engaged external cybersecurity professionals for a forensic investigation. Complimentary credit monitoring services were offered to affected individuals.

J jump to incidentP pin to compareR raw source

Leak gap clock✗ Leak >180d

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline

Nov 4, 2023

Begins

Apr 2, 2025

Filed

This filing is one of 9 records about the same incident.View merged incident

A leak claim by ransomhouse about this victim was first seen 476 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteransomhousebd_8f9a7248d821619c2023-12-13 · +476dVerified by operator

Regulatory filings (6) · sorted by filing gap

HHS OCRbd_36c97bfb1e2491ba2025-04-02Verified by operator
Montana State AGbd_78bee24c50a0bf152025-04-02Verified by operator
Indiana State AGbd_c59278804a53d6142025-04-02Verified by operator
Vermont State AGbd_db0571f01a4096d22025-04-02Verified by operator

Show 2 more filings ↓up to 1d gap

Massachusetts State AGbd_e35f6f18fda15ad82025-04-02Verified by operator
Illinois State AGbd_64809bc52fb8829c2025-04-01 · +1dVerified by operator

Press reports (1)

Pressransomhousebd_c5636cceee8c69592023-12-05 · +484dCandidate

Name: Dameron Hospital
norm: dameron hospital
Domain: dameronhospital.org

Name: Dameron Hospital
norm: dameron hospital
Domain: dameronhospital.org
Industry: Healthcarellm

Discovered: —
Breach occurred: Nov 4, 2023 – Nov 5, 2023
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)PHI
Attack vector: Unknown

During the incident: Commenced a prompt and thorough investigation
Working very closely with external cybersecurity professionals experienced in handling these types of incidents
Conducted extensive forensic investigation and comprehensive document review
Offering a complimentary membership of Experian IdentityWorks Credit 3B
Source: Quoted from the filing itself, not independently verified.

Compliance flags: Leak >180d
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 6 states

View merged incident ↗

Illinois State AGApr 1 · first

HHS OCR+1d

Montana State AG+1d

Indiana State AG+1d

Vermont State AG+1d

Massachusetts State AG+1d

California State AG+1d · this page

Evidence ladder

Leak-site claim

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

Press / market report

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

State AG / regulator filingThis record

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

SEC 8-K / victim statement

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

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-600811
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 2, 2025
Raw hash: d027092dd29826730c405874c95840c7db3285e9ad320fa44cd9d6a49a4518ed

Linked disclosures

Ransomware claims (1)

Regulatory filings (6) · sorted by filing gap

Press reports (1)

Reporting entityDameron Hospital

Victim entityDameron Hospital

IncidentUnknown

Stated responseCommenced a prompt and thorough investigation

ComplianceLeak >180d

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov