DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

ONEMAIN FINANCIAL GROUP, LLC — September 2017 breach

Clustered 2 filings across 2 jurisdictions · filing window Feb 9, 2018 → Feb 12, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

1

First → last filing

Feb 9, 2018 → Feb 12, 2018

Merge confidence

100%

incident inc_fee81a89200640d9 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Sep 1, 2017–Jan 16, 2018, discovered Jan 8, 2018 — the first regulatory filing landed 32 days later. 1 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
32days

Discovered → first regulatory filing

Filing span
3days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

Sep 1, 2017breach begins
Jan 8, 2018discovered
notification delay · 32 days
Feb 9, 2018first filing
Feb 12, 2018most 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. FEB 9NH AGNH AG noticefirst filing · 1 NH residentsday 0
  2. FEB 12SC AGSC AG noticemost recent · no count stated+3d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 1, 2017 – Jan 16, 2018
NH AG
Discovered
Jan 8, 2018· 129d undetected
NH AG
Data types
Identity (basic) · Financial account
NH AG + SC AG
Attack vector
Phishing
NH AG
Response
Launched an investigation into the nature and scope of the incident · Retained a leading team of data security experts to conduct a forensic investigation · Assisting law enforcement authorities with their investigation
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

3 days

vs. multi-state median

1.7× faster

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.