Confirmed breach. Intrusion Oct 24, 2023–Oct 29, 2023, discovered Oct 29, 2023 — the first regulatory filing landed 338 days later (flagged late). 8 individuals reported across the linked filings.
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 clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
8
Data types
—
Jurisdictions
2
ME VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 24, 2023 → Oct 29, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Oct 29, 2023
Reported by VERMONT AG filing
338 days
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
Medical Center Barbour notified consumers of a data breach detected on October 29, 2023. Unauthorized actors accessed files containing dates of birth, medical information, and health insurance information. The organization engaged forensic investigators and deployed additional monitoring. Affected individuals were offered 12 months of credit monitoring services.
Medical Center Barbour, a healthcare entity, reported an external system breach that occurred between October 24, 2023, and October 29, 2023. The breach was discovered on July 22, 2031, and affected 8 Maine residents. In response, the company offered 12 months of complimentary credit monitoring and identity protection services.
Affected (this filing): 8
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.