Confirmed breach. Intrusion Mar 22, 2023, discovered Jun 2, 2023 — the first regulatory filing landed 14 days later. 5 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont✓ VT AG ≤14 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
5
Data types
3
PII · Government ID · Health (basic)
Jurisdictions
1
VT
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 22, 2023
When the intrusion reportedly occurred, per the linked filings
Business Resource Services notified Vermont AG on June 16, 2023, of a misdelivery incident on March 22, 2023. PII including SSNs, birthdates, and health plan details were sent to a customer. 5 Rhode Island residents confirmed affected. BRS investigated, contacted recipient, and enhanced email security.
Affected (this filing): 5
VT AG ≤14 bday
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.