All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Novo Nordisk — October 2014 breach

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

✓ 0 discrepancies — filings agreeMerge92%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Nov 25, 2014 → Dec 18, 2014

Merge confidence

92%

incident inc_c0d3678be97f49b7 · merged by deterministic · confidence 92%

Part of the Automatic Data Processing, Inc. supply-chain incident (2014) — at least 3 organizations filed notifications naming this third party.

Confirmed breach. One breach, 2 legal records. Intrusion Oct 15, 2014, discovered Nov 13, 2014 — the first regulatory filing landed 12 days later. 2 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

12days

Discovered → first regulatory filing

Filing span

23days

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 15, 2014breach begins

Nov 13, 2014discovered

notification delay · 12 days

Nov 25, 2014first filing

Dec 18, 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

NOV 25NH AGNH AG noticefirst filing · 2 NH residentsday 0
DEC 18NH AGNH AG noticemost recent · 2 NH residents+23d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 15, 2014
Discovered: Nov 13, 2014· 29d undetected
Data types: Identity (basic) · Government ID
Attack vector: Third-Party / Supply Chain
Response: Vendor contacted the recipient and destroyed all copies of the report · Error that caused the report's disclosure has been redressed · Choosing to notify its employees and selected state agencies of this incident

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: 0.92 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (92% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

23 days

vs. multi-state median

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