DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

Brockton Area Multi-Services, Inc. — April 2023 breach

Clustered 7 filings across 6 jurisdictions · filing window May 16, 2024 → May 17, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

23,705

First → last filing

May 16, 2024 → May 17, 2024

Merge confidence

100%

incident inc_55a6c7a6251d4d1c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Apr 13, 2023, discovered Apr 14, 2023 — the first regulatory filing landed 398 days later (flagged late). 23,705 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 5 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
398days

Discovered → first regulatory filing

Discovery variance
381days

Range of discovered_at dates across filings

Filing span
1days

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.

Regulatory clocksVermont✗ VT AG >45 bdayHIPAA✓ HHS report on timeMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 18dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Apr 13, 2023breach begins
Apr 14, 2023discovered · members disagree
notification delay · 398 days
May 16, 2024first filing
May 17, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAY 16HHS OCRHHS OCR noticefirst filing · states nationwide total 21,537day 0
  2. MAY 16MT AGMT AG notice2 MT residentsday 0
  3. MAY 16IN AGIN AG noticestates nationwide total 23,705day 0
  4. MAY 16VT AGVT AG noticeno count statedday 0
  5. MAY 17MA AGMA AG notice12,055 MA residents+1d
  6. MAY 17ME AGME AG noticestates nationwide total 23,705+1d
  7. MAY 17NH AGNH AG noticemost recent · 30 NH residents+1d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 13, 2023
IN AG
Discovered
Apr 14, 2023MT AG + VT AG + NH AGApr 29, 2024HHS OCR + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
HHS OCR + VT AG + ME AG +3
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

23,705

Sum of filed state slices

12,103· 51.1% of stated

49% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US23,705
MA12,055
NH30
ME15
MT2
IN1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

1 days

Cadence

~1 / 0.2d

vs. multi-state median

9.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.