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

Prosper Marketplace, Inc. — April 2025 breach

Clustered 14 filings across 13 jurisdictions · filing window Sep 17, 2025 → Dec 11, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

14 filings

States

13

Affected · reported

13,076,476

First → last filing

Sep 17, 2025 → Dec 11, 2025

Merge confidence

100%

incident inc_281d9c902cd546a8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. The filings describe unauthorized access. Intrusion Apr 29, 2025–Sep 2, 2025, discovered Sep 1, 2025 — the first regulatory filing landed 16 days later (flagged late). 13,076,476 individuals reported across the linked filings. Data reported: Government ID, PII, Financial account, and 1 more. Notifications rolled out on a 85-day schedule across 14 filings beginning Sep 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
16days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Materiality delta
16days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
85days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksWashington✗ WA AG >90dOregon✗ OR AG >45dTexas✗ TX AG >30dMassachusetts✓ MA credit monitoring dueIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 29, 2025breach begins
Sep 1, 2025discovered
notification delay · 16 days
Sep 17, 2025first filing
Dec 11, 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. SEP 17SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. DEC 1IL AGIL AG noticeno count stated+75d
  3. DEC 9CA AGCA AG noticeno count stated+83d
  4. DEC 9WA AGWA AG notice249,848 WA residents+83d
  5. DEC 9MT AGMT AG notice33,808 MT residents+83d
  6. DEC 9IN AGIN AG noticestates nationwide total 13,076,476+83d
  7. DEC 9DE AGDE AG noticeno count stated+83d
  8. DEC 9MA AGMA AG notice189,828 MA residents+83d
  9. DEC 9OR AGOR AG noticestates nationwide total 13,076,476+83d
  10. DEC 9NE AGNE AG noticeno count stated+83d
  11. DEC 9IA AGIA AG notice1,008 IA residents+83d
  12. DEC 9NE AGNE AG noticeno count stated+83d
  13. DEC 10TX AGTX AG noticestates nationwide total 13,076,476+84d
  14. DEC 11SC AGSC AG noticemost recent · 236,019 SC residents+85d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 1, 2025 – Aug 31, 2025
CA AG
Discovered
Sep 1, 2025· 92d undetected
SEC 8-K + IL AG + CA AG +8
Data types
Financial account · Identity (basic) · Government ID · PII
SEC 8-K + IL AG + WA AG +8
Attack vector
Unauthorized Access
SEC 8-K

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)

13,076,476

Sum of filed state slices

2,147,986· 16.4% of stated

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

US13,076,476
TX1,161,581
IN275,894
WA249,848
SC236,019
MA189,828
MT33,808
IA1,008

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

85 days

Cadence

~1 / 6.5d

vs. multi-state median

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