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

EXPERIAN SERVICES CORP. — October 2014 breach

Clustered 2 filings across 1 jurisdiction · filing window Nov 3, 2014 → Nov 20, 2014. View entity profile → Other incidents for this victim →

✓ data types agreeMerge100%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

not comparable

First → last filing

Nov 3, 2014 → Nov 20, 2014

Merge confidence

100%

incident inc_50a8a4f93c564303 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe hacking. Intrusion Oct 20, 2014–Nov 20, 2014, discovered Nov 20, 2014. Data reported: Government ID, Identity (basic), and Financial account. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
17days

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.

Sensitive data

identity_government

Incident timeline

Oct 20, 2014breach begins
Nov 20, 2014discovered
Nov 3, 2014first filing
Nov 20, 2014most 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. NOV 3NH AGNH AG noticefirst filing · 2 NH residentsday 0
  2. NOV 20NH AGNH AG noticemost recent · 1 NH residents+17d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 20, 2014 – Oct 21, 2014
NH AG
Discovered
Nov 20, 2014· 31d undetected
NH AG
Data types
Identity (basic) · Government ID · Financial account
NH AG
Attack vector
Third-Party / Supply Chain
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

17 days

vs. multi-state median

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