MISSOURIHackingHealthcareHealthcareCustomer Data InvolvedPHIHealth (basic)Identity (basic)Low

CareSTL Health

bd_7a8c47c038ffad89 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Oct 3, 2025

To disclose

—

Affected

501

Linked

3 filings

Confidence

68%

Full breach record for CareSTL Health →

CareSTL Health, Inc. reported to HHS on 2025-10-03 a Hacking/IT Incident affecting 501 individuals. Breached information located on Network Server.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d

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

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Oct 3, 2025

Filed

—

Corroborated · see linked filings

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

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

A leak claim by kawa4096 about this victim predates this filing by 96 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Sitecephalusbd_3c0196a5b3c937262025-06-28 · +96dCandidate
Leak Sitekawa4096bd_5ab254cc104e2bda2025-06-28 · +96dVerified

Name: CareSTL Health
norm: carestl health
Domain: carestlhealth.org
Industry: Health Care Services

Name: CareSTL Health
norm: carestl health
Domain: carestlhealth.org
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 501nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Notified HHS OCR

Compliance flags: Leak >90dHHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

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://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Oct 3, 2025
Raw hash: 6bfaba1fa8cdb21cd0307fc8acbc2ed244624a91cb5e20cea3406dbaed8d66ea

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html976 B

Download View at source

Linked disclosures

Ransomware claims (2)

Reporting entityCareSTL Health

Victim entityCareSTL Health

IncidentUnauthorized Access

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing