DisclosureLens
UTAHHackingHealthcareHealthcareCustomer Data InvolvedHealth (basic)Low

STEEL ENCOUNTERS, INC.

bd_3a89b39e8b4a5f3a · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Dec 31, 2025

To disclose

—

Affected

959

Linked

4 filings

Confidence

93%
Full breach record for STEEL ENCOUNTERS, INC. →

Steel Encounters, Inc. (Utah healthcare provider) reported to HHS OCR on 2025-12-31 a Hacking/IT Incident affecting 959 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further details were provided in the HHS web description.

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

Dec 31, 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 4 about the same incident.View merged incident
A leak claim by akira about this victim predates this filing by 133 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 3 states

View merged incident ↗
Indiana State AGDec 31 · first
Nebraska State AGDec 31 · first
HHS OCRDec 31 · first · 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.