DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Big Brothers Big Sisters — March 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Nov 21, 2023 → Nov 27, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

35,072

First → last filing

Nov 21, 2023 → Nov 27, 2023

Merge confidence

100%

incident inc_9772e005e6644a3c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Mar 28, 2023, discovered Mar 28, 2023 — the first regulatory filing landed 238 days later (flagged late). 35,072 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 6 more. Notifications rolled out on a 6-day schedule across 8 filings beginning Nov 21, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
238days

Discovered → first regulatory filing

Discovery variance
232days

Range of discovered_at dates across filings

Filing span
6days

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 clocksWashington✗ WA AG >90dMaine✓ ME AG ≤30d · 7dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Mar 28, 2023breach begins
Mar 28, 2023discovered · members disagree
notification delay · 238 days
Nov 21, 2023first filing
Nov 27, 2023most 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. NOV 21MT AGMT AG noticefirst filing · 458 MT residentsday 0
  2. NOV 22DE AGDE AG noticeno count stated+1d
  3. NOV 22VT AGVT AG noticeno count stated+1d
  4. NOV 22WA AGWA AG notice15,604 WA residents+1d
  5. NOV 22NH AGNH AG notice35 NH residents+1d
  6. NOV 22ME AGME AG noticestates nationwide total 35,072+1d
  7. NOV 22CA AGCA AG noticeno count stated+1d
  8. NOV 27MA AGMA AG noticemost recent · 1,230 MA residents+6d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2023
MT AG
Discovered
Mar 28, 2023MT AG + WA AGNov 15, 2023DE AG + ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + DE AG + VT AG +5
Attack vector
Ransomware· Royal
MT AG

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)

35,072

Sum of filed state slices

17,450· 49.8% of stated

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

US35,072
WA15,604
MA1,230
MT458
ME123
NH35

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 filing8 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

6 days

Cadence

~1 / 0.9d

vs. multi-state median

1.5× 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.