DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedredalerthigh sensitivity
Merged incident · 11 filings

Bay Bridge Administrators — August 2022 breach

Clustered 11 filings across 11 jurisdictions · filing window Sep 22, 2022 → Jan 3, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

251,689

First → last filing

Sep 22, 2022 → Jan 3, 2023

Merge confidence

100%

incident inc_543e1f75e3134e45 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Aug 25, 2022–Sep 5, 2022, discovered Sep 5, 2022 — the first regulatory filing landed 115 days later (flagged late). 251,689 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 103-day schedule across 10 filings beginning Sep 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
115days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
98days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
103days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 115dOregon✗ OR AG >45dWashington✗ WA AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 25, 2022breach begins
Sep 5, 2022discovered
notification delay · 115 days
Dec 29, 2022first filing
Jan 3, 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. SEP 22Leak siteredalert postfirst filing · attacker claim · unverifiedday 0
  2. DEC 29ME AGME AG noticestates nationwide total 251,689+98d
  3. DEC 29OR AGOR AG noticestates nationwide total 251,689+98d
  4. DEC 29MA AGMA AG notice1,441 MA residents+98d
  5. DEC 29NH AGNH AG notice159 NH residents+98d
  6. DEC 29MT AGMT AG notice152 MT residents+98d
  7. DEC 29WA AGWA AG notice6,980 WA residents+98d
  8. DEC 29CA AGCA AG noticeno count stated+98d
  9. DEC 29IN AGIN AG noticestates nationwide total 251,689+98d
  10. DEC 30HHS OCRHHS OCR noticestates nationwide total 187,742+99d
  11. JAN 3SC AGSC AG noticemost recent · 1,093 SC residents+103d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 3, 2022
ME AG
Discovered
Sep 5, 2022· 2d undetected
ME AG + OR AG + NH AG +4
Data types
Health (basic) · Identity (basic) · Government ID · PHI
ME AG + NH AG + MT AG +5
Attack vector
Unauthorized Access
ME 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)

251,689

Sum of filed state slices

16,166· 6.4% of stated

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

US251,689
WA6,980
IN6,269
MA1,441
SC1,093
NH159
MT152
ME72

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 Aug 22, 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

103 days

Cadence

~1 / 10.3d

vs. multi-state median

11.4× slower

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.