Confirmed breach. Intrusion Oct 15, 2021, discovered Jul 1, 2022 — the first regulatory filing landed 28 days later. 66,118 individuals reported across the linked filings.
incident inc_3c21fe73a95b49b4 · merge_method human · confidence 100%
Litigation Timing
Notification delay
28days
Discovered → first regulatory filing
Filing span
7days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 28dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
66,118
Data types
2
Government ID · Identity (basic)
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 15, 2021
When the intrusion reportedly occurred, per the linked filings
Community Surgical Supply Inc. experienced an external system breach (hacking) on 10/15/2021, discovered on 07/01/2022. 66,115 individuals were affected, including 243 Maine residents. The breach exposed names and Social Security Numbers. The company provided written notification and 12 months of credit monitoring through Experian.
Affected (this filing): 66,115
ME AG ≤30d · 28d
🦬Montana State AGMost recentlinked via operator-confirmed · 100%
Community Surgical Supply reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-05. The breach occurred on 10/15/2021. 3 Montana residents were affected.
Affected (this filing): 3
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.