DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Progressive Leasing — September 2023 breach

Clustered 10 filings across 10 jurisdictions · filing window Sep 21, 2023 → Oct 30, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

193,055

First → last filing

Sep 21, 2023 → Oct 30, 2023

Merge confidence

100%

incident inc_1aee2ea070ab4ec6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Sep 9, 2023–Oct 11, 2023, discovered Sep 11, 2023 — the first regulatory filing landed 10 days later. 193,055 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 39-day schedule across 10 filings beginning Sep 21, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
10days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
39days

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.

Regulatory clocksMaine⏱ ME AG >30d · 42dWashington⏱ WA AG >30dCalifornia✓ CA 60-day OK · 42dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 9, 2023breach begins
Sep 11, 2023discovered
notification delay · 10 days
Sep 21, 2023first filing
Oct 30, 2023most 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. SEP 21SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. OCT 22CA AGCA AG noticeno count stated+31d
  3. OCT 23ME AGME AG noticestates nationwide total 193,055+32d
  4. OCT 23MT AGMT AG notice40 MT residents+32d
  5. OCT 23OR AGOR AG noticestates nationwide total 193,055+32d
  6. OCT 23DE AGDE AG noticeno count stated+32d
  7. OCT 23MA AGMA AG notice2,541 MA residents+32d
  8. OCT 24WA AGWA AG noticestates nationwide total 193,055+33d
  9. OCT 24SC AGSC AG notice4,436 SC residents+33d
  10. OCT 30NH AGNH AG noticemost recent · states nationwide total 193,055+39d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 9, 2023
CA AG
Discovered
Sep 11, 2023· 2d undetected
CA AG + ME AG + MT AG +5
Data types
Financial account · Identity (basic) · Government ID · PII
SEC 8-K + SC AG + NH AG +6
Attack vector
Unauthorized Access
CA 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)

193,055

Sum of filed state slices

10,603· 5.5% of stated

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

US193,055
SC4,436
WA2,582
MA2,541
NH516
ME488
MT40

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 statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

39 days

Cadence

~1 / 4.3d

vs. multi-state median

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