DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed14 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 14 filings

WEL Companies — January 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

12

Affected · reported

122,960

First → last filing

Jan 31, 2025 → Nov 25, 2025

Merge confidence

100%

incident inc_f15c37bd8c3c4562 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 2 unverified claims. Intrusion Jan 30, 2025–Mar 28, 2025, discovered Jan 30, 2025 — the first regulatory filing landed 275 days later (flagged late). 122,960 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 298-day schedule across 12 filings beginning Jan 31, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
275days

Discovered → first regulatory filing

Discovery variance
286days

Range of discovered_at dates across filings

Leak precedence
274days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
298days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 292dOregon✗ OR AG >45dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 30, 2025breach begins
Jan 30, 2025discovered · members disagree
notification delay · 275 days
Nov 1, 2025first filing
Nov 25, 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 31Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. FEB 19Leak siteransomhub postattacker claim · unverified+19d
  3. NOV 1IL AGIL AG noticeno count stated+274d
  4. NOV 18MT AGMT AG notice231 MT residents+291d
  5. NOV 18IN AGIN AG noticestates nationwide total 122,960+291d
  6. NOV 18DE AGDE AG noticeno count stated+291d
  7. NOV 19NH AGNH AG notice592 NH residents+292d
  8. NOV 19ME AGME AG noticestates nationwide total 122,960+292d
  9. NOV 19OR AGOR AG noticestates nationwide total 122,960+292d
  10. NOV 19WA AGWA AG notice978 WA residents+292d
  11. NOV 19CA AGCA AG noticeno count stated+292d
  12. NOV 20SC AGSC AG notice2,214 SC residents+293d
  13. NOV 21MA AGMA AG notice1,288 MA residents+294d
  14. NOV 25TX AGTX AG noticemost recent · states nationwide total 122,960+298d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2025
MT AG
Discovered
Jan 30, 2025OR AGJan 31, 2025IL AG + MT AG + NH AG +4Mar 28, 2025TX AGNov 12, 2025DE AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + WA AG + TX AG +7
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)

122,960

Sum of filed state slices

22,246· 18.1% of stated

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

US122,960
TX13,157
IN3,271
SC2,214
MA1,288
WA978
NH592
ME515
MT231

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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 23, 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

298 days

Cadence

~1 / 22.9d

vs. multi-state median

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