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

American Lending Center — July 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Apr 28, 2026 → May 27, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

123,158

First → last filing

Apr 28, 2026 → May 27, 2026

Merge confidence

100%

incident inc_fc2fc8b94284412e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Jul 1, 2025–Jul 31, 2025, discovered Jul 27, 2025 — the first regulatory filing landed 275 days later (flagged late). 123,158 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 4 more. Notifications rolled out on a 29-day schedule across 11 filings beginning Apr 28, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
275days

Discovered → first regulatory filing

Discovery variance
255days

Range of discovered_at dates across filings

Filing span
29days

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 · 288dOregon✗ OR AG >45dWashington✗ WA AG >90dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Jul 1, 2025breach begins
Jul 27, 2025discovered · members disagree
notification delay · 275 days
Apr 28, 2026first filing
May 27, 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. APR 28NE AGNE AG noticefirst filing · no count statedday 0
  2. APR 28IN AGIN AG noticestates nationwide total 123,158day 0
  3. MAY 11MA AGMA AG notice942 MA residents+13d
  4. MAY 11ME AGME AG noticestates nationwide total 123,158+13d
  5. MAY 11CA AGCA AG noticeno count stated+13d
  6. MAY 12OR AGOR AG noticestates nationwide total 123,158+14d
  7. MAY 13WA AGWA AG notice6,049 WA residents+15d
  8. MAY 13VT AGVT AG notice41 VT residents+15d
  9. MAY 14TX AGTX AG noticestates nationwide total 123,158+16d
  10. MAY 18SC AGSC AG notice1,725 SC residents+20d
  11. MAY 27NH AGNH AG noticemost recent · 81 NH residents+29d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 1, 2025
NE AG
Discovered
Jul 27, 2025ME AG + OR AG + WA AG +1Apr 8, 2026NE AG + NH AGfilings disagree on discovery
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
NE AG + MA AG + ME AG +6
Attack vector
Ransomware
NE 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)

123,158

Sum of filed state slices

17,685· 14.4% of stated

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

US123,158
TX7,644
WA6,049
SC1,725
IN1,083
MA942
ME120
NH81
VT41

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

29 days

Cadence

~1 / 2.9d

vs. multi-state median

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