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

LexisNexis Risk Solutions FL Inc. — December 2024 breach

Clustered 17 filings across 16 jurisdictions · filing window May 1, 2025 → Jun 3, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

16

Affected · reported

364,333

First → last filing

May 1, 2025 → Jun 3, 2025

Merge confidence

100%

incident inc_6525df5034bd4937 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. The filings describe hacking. Intrusion Dec 25, 2024, discovered Apr 1, 2025 — the first regulatory filing landed 30 days later (flagged late). 364,333 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 33-day schedule across 17 filings beginning May 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
43days

Range of discovered_at dates across filings

Filing span
33days

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 clocksIowa✗ IA AG >5 bdayWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdaySouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 31dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 13dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 25, 2024breach begins
Apr 1, 2025discovered · members disagree
notification delay · 30 days
May 1, 2025first filing
Jun 3, 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. MAY 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 1IL AGIL AG noticeno count statedday 0
  3. MAY 24MT AGMT AG notice1,442 MT residents+23d
  4. MAY 27DE AGDE AG noticeno count stated+26d
  5. MAY 27SC AGSC AG notice4,770 SC residents+26d
  6. MAY 27WA AGWA AG notice17,430 WA residents+26d
  7. MAY 27CA AGCA AG noticeno count stated+26d
  8. MAY 27MA AGMA AG notice6,222 MA residents+26d
  9. MAY 27IA AGIA AG notice2,359 IA residents+26d
  10. MAY 27IN AGIN AG noticestates nationwide total 364,333+26d
  11. MAY 27NE AGNE AG noticeno count stated+26d
  12. MAY 27VT AGVT AG noticeno count stated+26d
  13. MAY 27ME AGME AG noticestates nationwide total 364,333+26d
  14. MAY 27OR AGOR AG noticestates nationwide total 364,333+26d
  15. MAY 29TX AGTX AG noticestates nationwide total 364,333+28d
  16. JUN 3RI AGRI AG notice634 RI residents+33d
  17. JUN 3NH AGNH AG noticemost recent · 717 NH residents+33d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2024
MT AG
Discovered
Apr 1, 2025IL AG + MT AG + DE AG +8May 14, 2025IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
IL AG + MT AG + DE AG +11
Attack vector
Third-Party / Supply Chain
MT 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)

364,333

Sum of filed state slices

71,353· 19.6% of stated

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

US364,333
TX28,933
WA17,430
IN8,185
MA6,222
SC4,770
IA2,359
MT1,442
NH717
ME661
RI634

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 filing17 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 Jun 12, 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

33 days

Cadence

~1 / 2.1d

vs. multi-state median

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