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

Community Loan Servicing — October 2021 breach

Clustered 9 filings across 9 jurisdictions · filing window Aug 19, 2022 → Dec 8, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

116,803

First → last filing

Aug 19, 2022 → Dec 8, 2022

Merge confidence

100%

incident inc_ef44f7c81b8147b5 · merged by deterministic · confidence 100%

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

Litigation Timing

Supplemental
Notification delay
261days

Discovered → first regulatory filing

Discovery variance
240days

Range of discovered_at dates across filings

Filing span
111days

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 clocksWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueHawaii✓ HI 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 · 261 days
Aug 19, 2022first filing
Dec 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. AUG 19MT AGMT AG noticefirst filing · 828 MT residentsday 0
  2. AUG 19MA AGMA AG notice1,749 MA residentsday 0
  3. AUG 19OR AGOR AG noticestates nationwide total 116,803day 0
  4. AUG 19IN AGIN AG noticestates nationwide total 116,803day 0
  5. AUG 19WA AGWA AG notice7,518 WA residentsday 0
  6. AUG 19DE AGDE AG notice678 DE residentsday 0
  7. AUG 19CA AGCA AG noticeno count statedday 0
  8. AUG 22SC AGSC AG notice3,401 SC residents+3d
  9. DEC 8HI AGHI AG noticemost recent · 1,447 HI residents+111d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

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

116,803

Sum of filed state slices

17,802· 15.2% of stated

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

US116,803
WA7,518
SC3,401
IN2,181
MA1,749
HI1,447
MT828
DE678

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

111 days

Cadence

~1 / 13.9d

vs. multi-state median

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