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

Fried, Frank, Harris, Shriver & Jacobson LLP — October 2025 breach

Clustered 18 filings across 12 jurisdictions · filing window Jan 12, 2026 → Mar 9, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

18 filings

States

12

Affected · reported

179,613

First → last filing

Jan 12, 2026 → Mar 9, 2026

Merge confidence

100%

incident inc_86214df31bd246f5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 18 regulatory filings. The filings describe unauthorized access. Intrusion Oct 23, 2025–Oct 28, 2025, discovered Oct 27, 2025 — the first regulatory filing landed 77 days later (flagged late). 179,613 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 56-day schedule across 18 filings beginning Jan 12, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
77days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
56days

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 >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 95dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 23, 2025breach begins
Oct 27, 2025discovered
notification delay · 77 days
Jan 12, 2026first filing
Mar 9, 2026most 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. JAN 12NH AGNH AG noticefirst filing · 2 NH residentsday 0
  2. JAN 30IN AGIN AG noticestates nationwide total 46,602+18d
  3. JAN 30IN AGIN AG noticestates nationwide total 46,602+18d
  4. JAN 30NE AGNE AG noticeno count stated+18d
  5. JAN 30CA AGCA AG noticeno count stated+18d
  6. JAN 30WA AGWA AG notice2,106 WA residents+18d
  7. JAN 30OR AGOR AG noticestates nationwide total 46,602+18d
  8. JAN 30ME AGME AG noticestates nationwide total 46,602+18d
  9. JAN 31MA AGMA AG notice1,391 MA residents+19d
  10. FEB 2NH AGNH AG notice143 NH residents+21d
  11. MAR 6VT AGVT AG noticeno count stated+53d
  12. MAR 6SC AGSC AG notice1,946 SC residents+53d
  13. MAR 6NE AGNE AG noticeno count stated+53d
  14. MAR 6IA AGIA AG notice1,029 IA residents+53d
  15. MAR 6ME AGME AG notice225 ME residents+53d
  16. MAR 6CA AGCA AG noticeno count stated+53d
  17. MAR 9TX AGTX AG noticestates nationwide total 179,613+56d
  18. MAR 9NH AGNH AG noticemost recent · 185 NH residents+56d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 23, 2025
IN AG
Discovered
Oct 27, 2025· 4d undetected
NH AG + NE AG + WA AG +7
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + NE AG + WA AG +7
Attack vector
Unauthorized Access
NH 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)

179,613

Sum of filed state slices

27,074· 15.1% of stated

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

US179,613
TX16,724
IN3,468
WA2,106
SC1,946
MA1,391
IA1,029
ME225
NH185

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 filing18 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 10, 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

56 days

Cadence

~1 / 3.3d

vs. multi-state median

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