Clustered 2 filings across 2 jurisdictions · filing window Aug 25, 2025 → Aug 26, 2025. View entity profile → Other incidents for this victim →
incident inc_4b1c6f9733404533 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
OR TX
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 27, 2024 → Oct 3, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 3, 2025
Reported by OREGON AG, TEXAS AG filings
Healthcare Services Group, Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2025-08-25. The breach occurred during 9/27/2024 - 10/3/2024. The breach was discovered on 6/3/2025. 624,496 individuals were affected. Notice was sent on 8/25/2025.
Affected (this filing): 624,496
Healthcare Services Group, Inc based in Bensalem, Pennsylvania, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-06-03 and reported on 2025-08-26. 82,280 Texas residents were affected. 624,496 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
Affected (this filing): 82,280
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.