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

Berman & Rabin — July 2024 breach

Clustered 13 filings across 13 jurisdictions · filing window Jan 1, 2025 → Jan 29, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

13

Affected · reported

151,944

First → last filing

Jan 1, 2025 → Jan 29, 2025

Merge confidence

100%

incident inc_c54a70d318524d96 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe malware. Intrusion Jul 5, 2024–Jul 8, 2024, discovered Jul 5, 2024 — the first regulatory filing landed 180 days later (flagged late). 151,944 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 28-day schedule across 13 filings beginning Jan 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
180days

Discovered → first regulatory filing

Discovery variance
95days

Range of discovered_at dates across filings

Filing span
28days

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 >90dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 199dMaine✗ ME AG >90d · 204dIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 5, 2024breach begins
Jul 5, 2024discovered · members disagree
notification delay · 180 days
Jan 1, 2025first filing
Jan 29, 2025most 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 28NE AGNE AG notice468 NE residents+27d
  3. JAN 28DE AGDE AG noticeno count stated+27d
  4. JAN 28WA AGWA AG notice6,846 WA residents+27d
  5. JAN 28NH AGNH AG notice261 NH residents+27d
  6. JAN 28IA AGIA AG notice763 IA residents+27d
  7. JAN 28IN AGIN AG noticestates nationwide total 151,944+27d
  8. JAN 28MT AGMT AG notice787 MT residents+27d
  9. JAN 28VT AGVT AG noticeno count stated+27d
  10. JAN 28OR AGOR AG noticestates nationwide total 151,893+27d
  11. JAN 28CA AGCA AG noticeno count stated+27d
  12. JAN 28ME AGME AG noticestates nationwide total 151,944+27d
  13. JAN 29SC AGSC AG noticemost recent · 2,811 SC residents+28d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 5, 2024 – Jul 8, 2024
NE AG
Discovered
Jul 5, 2024IL AGJul 8, 2024NE AG + DE AG + WA AG +7Oct 8, 2024OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NE AG + DE AG + WA AG +7
Attack vector
Ransomware
NE 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)

151,944

Sum of filed state slices

13,987· 9.2% of stated

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

US151,944
WA6,846
SC2,811
IN1,804
MT787
IA763
NE468
NH261
ME247

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 filing13 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

28 days

Cadence

~1 / 2.3d

vs. multi-state median

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