Clustered 3 filings across 3 jurisdictions · filing window Nov 18, 2025 → Dec 2, 2025. View entity profile → Other incidents for this victim →
incident inc_088b9b2a1e714b66 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
Health (basic)
MA NH VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 18, 2025 → Sep 19, 2025
When the intrusion reportedly occurred, per the linked filings
Sep 19, 2025
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Dermatology Associates of Concord (MA) reported to HHS OCR on 2025-11-18 a Hacking/IT Incident affecting 501 individuals. Breached information was located on a Network Server. No business associate was identified. No further details were provided in the HHS web description.
Affected (this filing): 501
Dermatology Associates of Concord notified consumers of a cyber-attack where an unauthorized actor accessed a specific system and copied files containing names between Sept 18-19, 2025. The incident was discovered on Sept 19, 2025. No evidence of fraud was found. The organization engaged third-party cybersecurity experts, notified law enforcement, enhanced security protocols, and is offering 24 months of credit monitoring services.
Dermatology Associates of Concord (DAC) notified the New Hampshire Attorney General of a data event affecting 17 NH residents. Unauthorized access occurred between Sept 18-19, 2025, involving copying of files containing names, SSNs, driver's licenses, passports, and medical info. DAC engaged third-party cybersecurity experts, notified law enforcement, and provided 2 years of TransUnion credit monitoring. Investigation is ongoing.
Affected (this filing): 17
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.