Confirmed breach. Intrusion Nov 4, 2024, discovered Nov 5, 2024 — the first regulatory filing landed 135 days later (flagged late). 1 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaryland✗ MD AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
MD
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 4, 2024
When the intrusion reportedly occurred, per the linked filings
Crown Health Care Laundry Services notified Maryland AG of a data incident on March 20, 2025. Unauthorized access occurred Nov 4, 2024; discovered Nov 5. One Maryland resident affected; data included name and SSN. Forensic consultants engaged, law enforcement notified. Credit monitoring offered.
Affected (this filing): 1
MD AG >90d
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.