DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 7 records

Intelliloan — March 2025 breach

Clustered 7 records across 4 jurisdictions: 4 filings and 3 leak-site claims · filing window May 8, 2025 → Sep 26, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

4

Affected · reported

6,071

First → last filing

May 8, 2025 → Sep 26, 2025

Merge confidence

100%

incident inc_bc58c48ea6634105 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 3 unverified claims. The filing describes hacking. Intrusion Mar 29, 2025–Mar 30, 2025, discovered Mar 29, 2025 — the first regulatory filing landed 40 days later; 2 later filings were flagged late. 6,071 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 141-day schedule across 4 filings beginning May 8, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
40days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Leak precedence
38days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
141days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 60-day late · 156dTexas✗ TX AG >30dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 29, 2025breach begins
Mar 29, 2025discovered · members disagree
notification delay · 40 days
May 8, 2025first filing
Sep 26, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. MAR 30Leak sitelockbit5 postfirst record · attacker claim · unverifiedday 0
  2. MAR 30Leak siteransomhub postattacker claim · unverified+1d
  3. APR 3Leak sitelockbit_3 postattacker claim · unverified+4d
  4. MAY 8OR AGOR AG noticestates nationwide total 250+39d
  5. SEP 25CA AGCA AG noticeno count stated+179d
  6. SEP 26TX AGTX AG noticestates nationwide total 6,071+180d
  7. SEP 26MA AGMA AG noticemost recent · 43 MA residents+180d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 29, 2025 – Mar 30, 2025
OR AG
Discovered
Mar 29, 2025CA AG + TX AGMar 30, 2025OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
CA AG + TX AG + MA 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)

6,071

Sum of filed state slices

432· 7.1% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim3 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

141 days

Cadence

~1 / 47d

vs. multi-state median

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