DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbitlockerhigh sensitivity
Merged incident · 7 filings

State Bar of Georgia — April 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window May 2, 2022 → Oct 7, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

52,159

First → last filing

May 2, 2022 → Oct 7, 2022

Merge confidence

100%

incident inc_7b56afb7a6b84f28 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 28, 2022–Sep 20, 2022, discovered Apr 28, 2022 — the first regulatory filing landed 162 days later (flagged late). 52,159 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 158-day schedule across 6 filings beginning May 2, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
162days

Discovered → first regulatory filing

Leak precedence
158days 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
158days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine✗ ME AG >90d · 162dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 28, 2022breach begins
Apr 28, 2022discovered
notification delay · 162 days
Oct 7, 2022first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. MAY 2Leak sitebitlocker postfirst filing · attacker claim · unverifiedday 0
  2. OCT 7NH AGNH AG notice23 NH residents+158d
  3. OCT 7ME AGME AG noticestates nationwide total 52,159+158d
  4. OCT 7IN AGIN AG noticestates nationwide total 52,159+158d
  5. OCT 7MT AGMT AG notice22 MT residents+158d
  6. OCT 7CA AGCA AG noticeno count stated+158d
  7. OCT 7MA AGMA AG noticemost recent · 176 MA residents+158d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 28, 2022
NH AG
Discovered
Apr 28, 2022
ME AG
Data types
Financial account · Identity (basic) · Government ID
NH AG + ME AG + MT AG +2
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)

52,159

Sum of filed state slices

329· 0.6% of stated

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

US52,159
MA176
IN83
ME25
NH23
MT22

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 filing6 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 23, 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

158 days

Cadence

~1 / 26.3d

vs. multi-state median

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