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

Pingora Loan Servicing, LLC — October 2021 breach

Clustered 11 filings across 11 jurisdictions · filing window Jan 1, 2022 → Apr 8, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

1,268,248

First → last filing

Jan 1, 2022 → Apr 8, 2022

Merge confidence

100%

incident inc_abb0c42e69794da9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Oct 27, 2021–Dec 7, 2021, discovered Dec 1, 2021 — the first regulatory filing landed 31 days later (flagged late). 1,268,248 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 97-day schedule across 11 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
96days

Range of discovered_at dates across filings

Filing span
97days

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 clocksCalifornia✗ CA 60-day late · 96dWashington✗ WA AG >90dHawaii✓ HI CRA notice dueOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 27, 2021breach begins
Dec 1, 2021discovered · members disagree
notification delay · 31 days
Jan 1, 2022first filing
Apr 8, 2022most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 6IN AGIN AG noticestates nationwide total 1,268,248+95d
  3. APR 6HI AGHI AG notice7,002 HI residents+95d
  4. APR 6MT AGMT AG notice3,746 MT residents+95d
  5. APR 6CA AGCA AG noticeno count stated+95d
  6. APR 6NH AGNH AG notice8,951 NH residents+95d
  7. APR 6OR AGOR AG noticestates nationwide total 1,268,248+95d
  8. APR 6DE AGDE AG noticeno count stated+95d
  9. APR 6WA AGWA AG notice52,606 WA residents+95d
  10. APR 7MA AGMA AG notice21,218 MA residents+96d
  11. APR 8SC AGSC AG noticemost recent · 20,361 SC residents+97d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 27, 2021
IN AG
Discovered
Dec 1, 2021IL AG + HI AG + MT AG +4Dec 6, 2021WA AGMar 7, 2022OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
HI AG + MT AG + CA AG +5
Attack vector
Unauthorized Access
HI 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)

1,268,248

Sum of filed state slices

130,822· 10.3% of stated

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

US1,268,248
WA52,606
MA21,218
SC20,361
IN16,938
NH8,951
HI7,002
MT3,746

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

97 days

Cadence

~1 / 9.7d

vs. multi-state median

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