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

Berkeley Research Group, LLC — February 2025 breach

Clustered 18 filings across 14 jurisdictions · filing window Oct 1, 2025 → Sep 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

18 filings

States

14

Affected · reported

not comparable

First → last filing

Oct 1, 2025 → Sep 1, 2026

Merge confidence

100%

incident inc_2e6b0e13f48040fa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 18 regulatory filings. Intrusion Feb 28, 2025–Mar 2, 2025, discovered Mar 2, 2025 — the first regulatory filing landed 213 days later (flagged late). Data reported: Government ID, Authentication, Financial account, and 7 more. Notifications rolled out on a 335-day schedule across 18 filings beginning Oct 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
213days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
335days

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 clocksMaine✗ ME AG >90d · 242dOregon✗ OR AG >45dWashington✗ WA AG >90dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Feb 28, 2025breach begins
Mar 2, 2025discovered
notification delay · 213 days
Oct 1, 2025first filing
Sep 1, 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. OCT 1IL AGIL AG noticefirst filing · no count statedday 0
  2. OCT 30DE AGDE AG noticeno count stated+29d
  3. OCT 30ME AGME AG noticestates nationwide total 6,083+29d
  4. OCT 30MA AGMA AG notice5 MA residents+29d
  5. OCT 30CA AGCA AG noticeno count stated+29d
  6. OCT 30SC AGSC AG notice14,620 SC residents+29d
  7. OCT 30OR AGOR AG noticestates nationwide total 6,083+29d
  8. OCT 30WA AGWA AG notice17,188 WA residents+29d
  9. OCT 30IN AGIN AG noticestates nationwide total 6,083+29d
  10. OCT 30WA AGWA AG notice15 WA residents+29d
  11. OCT 30IA AGIA AG noticeno count stated+29d
  12. OCT 30NE AGNE AG noticeno count stated+29d
  13. OCT 30VT AGVT AG noticeno count stated+29d
  14. NOV 3NH AGNH AG notice1 NH residents+33d
  15. NOV 4TX AGTX AG noticestates nationwide total 6,083+34d
  16. AUG 31CA AGCA AG noticeno count stated+334d
  17. AUG 31VT AGVT AG notice1,314 VT residents+334d
  18. SEP 1TX AGTX AG noticemost recent · 92,290 affected+335d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 28, 2025 – Mar 2, 2025
DE AG
Discovered
Mar 2, 2025· 2d undetected
IL AG + DE AG + ME AG +9
Data types
Authentication · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
IL AG + WA AG + MA AG +9
Attack vector
Unauthorized Access
DE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US6,083
TX92,290
WA17,188
SC14,620
VT1,314
MA5
IN3
NH1

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

335 days

Cadence

~1 / 19.7d

vs. multi-state median

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