DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedegregorhigh sensitivity
Merged incident · 10 filings

SN Servicing Corporation — October 2020 breach

Clustered 10 filings across 8 jurisdictions · filing window Oct 15, 2020 → Jul 26, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

170,426

First → last filing

Oct 15, 2020 → Jul 26, 2021

Merge confidence

100%

incident inc_419b9fed142b427b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion Oct 14, 2020–Oct 15, 2020, discovered Oct 15, 2020 — the first regulatory filing landed 78 days later (flagged late). 170,426 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 284-day schedule across 9 filings beginning Oct 15, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
78days

Discovered → first regulatory filing

Discovery variance
40days

Range of discovered_at dates across filings

Leak precedence
78days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
284days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 274dCalifornia✗ CA 60-day late · 194dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 14, 2020breach begins
Oct 15, 2020discovered · members disagree
notification delay · 78 days
Jan 1, 2021first filing
Jul 26, 2021most 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. OCT 15Leak siteegregor postfirst filing · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticeno count stated+78d
  3. JAN 15NH AGNH AG notice8 NH residents+92d
  4. JAN 15IN AGIN AG noticestates nationwide total 20,155+92d
  5. JAN 15ME AGME AG noticestates nationwide total 20,155+92d
  6. JAN 29CA AGCA AG noticeno count stated+106d
  7. JUL 16CA AGCA AG noticeno count stated+274d
  8. JUL 16ME AGME AG noticestates nationwide total 170,426+274d
  9. JUL 16OR AGOR AG noticestates nationwide total 170,426+274d
  10. JUL 26SC AGSC AG noticemost recent · 3,179 SC residents+284d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 14, 2020 – Oct 15, 2020
NH AG
Discovered
Oct 15, 2020IL AG + NH AG + CA AG +3Nov 24, 2020ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
NH AG + ME AG + CA AG +1
Attack vector
Ransomware· Mount Locker
NH 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)

170,426

Sum of filed state slices

4,358· 2.6% of stated

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

US170,426
SC3,179
IN787
ME384
NH8

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

284 days

Cadence

~1 / 31.6d

vs. multi-state median

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