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

UNIVERSAL LENDERS, LLC — November 2024 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

19,575

First → last filing

Jan 1, 2025 → Nov 13, 2025

Merge confidence

100%

incident inc_26995a1eef564732 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Nov 7, 2024, discovered Nov 7, 2024 — the first regulatory filing landed 55 days later (flagged late). 19,575 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 316-day schedule across 9 filings beginning Jan 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
55days

Discovered → first regulatory filing

Discovery variance
68days

Range of discovered_at dates across filings

Filing span
316days

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 clocksVermont✗ VT AG >45 bdayMaine✓ ME AG ≤30d · 9dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 7, 2024breach begins
Nov 7, 2024discovered · members disagree
notification delay · 55 days
Jan 1, 2025first filing
Nov 13, 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 21MT AGMT AG notice100 MT residents+20d
  3. JAN 21VT AGVT AG noticeno count stated+20d
  4. JAN 21NE AGNE AG noticeno count stated+20d
  5. JAN 21IN AGIN AG noticestates nationwide total 19,575+20d
  6. JAN 21NH AGNH AG notice80 NH residents+20d
  7. JAN 23ME AGME AG noticestates nationwide total 19,575+22d
  8. JAN 24MA AGMA AG notice520 MA residents+23d
  9. NOV 13MD AGMD AG noticemost recent · 119 MD residents+316d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 7, 2024
MT AG
Discovered
Nov 7, 2024IL AG + MT AG + VT AG +3Jan 14, 2025ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
MT AG + VT AG + NE AG +4
Attack vector
Unauthorized Access
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)

19,575

Sum of filed state slices

1,267· 6.5% of stated

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

US19,575
MA520
IN414
MD119
MT100
NH80
ME34

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

316 days

Cadence

~1 / 39.5d

vs. multi-state median

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