All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed8 filings · 8 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 8 filings

NISSAN NORTH AMERICA, INC. — October 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window May 14, 2024 → May 15, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

53,038

First → last dated filing

May 14, 2024 → May 15, 2024

Merge confidence

100%

incident inc_231fcfd5cfb8458a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Oct 18, 2023–Nov 7, 2023, discovered Nov 7, 2023. 53,038 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

113days

Range of discovered_at dates across filings

Filing span

1days

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 clocksCalifornia✗ CA 60-day late · 190dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 76dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 18, 2023breach begins

Nov 7, 2023discovered · members disagree

May 14, 2024first dated filing

May 15, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

MAY 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
MAY 14MA AGMA AG noticefirst filing · 152 MA residentsauto-linkedday 0
MAY 14MT AGMT AG notice13 MT residentsday 0
MAY 14CA AGCA AG noticeno count statedauto-linkedday 0
MAY 14ME AGME AG noticestates nationwide total 53,038operator-confirmedday 0
MAY 14NH AGNH AG notice22 NH residentsauto-linkedday 0
MAY 15VT AGVT AG noticeno count statedauto-linked+1d
MAY 15IN AGIN AG noticemost recent · states nationwide total 53,038auto-linked+1d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 7, 2023
Discovered: Nov 7, 2023IL AG + MT AG + CA AG +2Feb 28, 2024ME AGfilings disagree on discovery
Data types: Employment · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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)

53,038

Sum of filed state slices

278· 0.5% of stated

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

US53,038

MA152

IN82

NH22

MT13

ME9

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

1 days

Cadence

~1 / 0.2d

vs. multi-state median

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