Clustered 3 filings across 3 jurisdictions · filed Aug 15, 2024. View entity profile → Other incidents for this victim →
incident inc_97140a4825b24e71 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
PHI · Health (basic)
MT NH TN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 11, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 18, 2023
Reported by NEW HAMPSHIRE AG filing
Specialty Networks, Inc. notified the NH Attorney General of a data security incident affecting 24 NH residents. Unauthorized access occurred around Dec 11, 2023; detected Dec 18, 2023. PHI and PII were potentially compromised. Forensic investigation engaged; FBI notified. Notifications sent Aug 15, 2024, with credit monitoring offered.
Affected (this filing): 24
Specialty Networks, Inc. (TN), a Business Associate, reported to HHS OCR on 2024-08-15 a Hacking/IT Incident affecting 411,037 individuals. Breached information was located on a Network Server. A business associate was present.
Affected (this filing): 411,037
Specialty Networks, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-08-15. The breach occurred on 12/11/2023. 27 Montana residents were affected.
Affected (this filing): 27
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.