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

700Credit, LLC — October 2025 breach

Clustered 18 filings across 17 jurisdictions · filing window Nov 21, 2025 → Dec 22, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

18 filings

States

17

Affected · reported

6,076,262

First → last filing

Nov 21, 2025 → Dec 22, 2025

Merge confidence

100%

incident inc_fdcab8591c91415a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 18 regulatory filings. The filings describe unauthorized access. Intrusion Oct 25, 2025–Oct 27, 2025, discovered Oct 25, 2025 — the first regulatory filing landed 27 days later (flagged late). 6,076,262 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 31-day schedule across 18 filings beginning Nov 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
27days

Discovered → first regulatory filing

Discovery variance
27days

Range of discovered_at dates across filings

Filing span
31days

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 clocksOregon✗ OR AG >45dMaine⏱ ME AG >30d · 48dWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdayIowa✓ IA AG ≤5 bdayMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 25, 2025breach begins
Oct 25, 2025discovered · members disagree
notification delay · 27 days
Nov 21, 2025first filing
Dec 22, 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. NOV 21WI AGWI AG noticefirst filing · 5,600,000 affectedday 0
  2. DEC 1IL AGIL AG noticeno count stated+10d
  3. DEC 12IA AGIA AG notice46,107 IA residents+21d
  4. DEC 12ME AGME AG notice0 affected+21d
  5. DEC 12CA AGCA AG noticeno count stated+21d
  6. DEC 12MT AGMT AG notice17,296 MT residents+21d
  7. DEC 12MA AGMA AG notice79,810 MA residents+21d
  8. DEC 12NH AGNH AG notice25,271 NH residents+21d
  9. DEC 12ME AGME AG noticestates nationwide total 5,836,521+21d
  10. DEC 12OR AGOR AG noticestates nationwide total 5,836,521+21d
  11. DEC 12WA AGWA AG notice121,828 WA residents+21d
  12. DEC 15SC AGSC AG notice108,829 SC residents+24d
  13. DEC 16TX AGTX AG noticestates nationwide total 5,836,521+25d
  14. DEC 18ID AGID AG notice38,405 ID residents+27d
  15. DEC 22NE AGNE AG notice38,716 NE residents+31d
  16. DEC 22IN AGIN AG noticestates nationwide total 583,652+31d
  17. DEC 22VT AGVT AG noticeno count stated+31d
  18. DEC 22DE AGDE AG noticemost recent · no count stated+31d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 25, 2025
WI AG
Discovered
Oct 25, 2025IA AG + ME AG + CA AG +9Nov 21, 2025IL AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
WI AG + IL AG + IA AG +12
Attack vector
Unauthorized Access
IA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US5,836,521
WI5,600,000
TX709,406
WA121,828
SC108,829
IN87,639
MA79,810
IA46,107
NE38,716
ID38,405
NH25,271
ME19,225
MT17,296

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

31 days

Cadence

~1 / 1.8d

vs. multi-state median

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