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

TD Bank, National Association — November 2023 breach

Clustered 2 filings across 2 jurisdictions · filed Dec 24, 2025 (dated filings only). View entity profile → Other incidents for this victim →

✓ data types agreeMerge43%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

1

First → last dated filing

Dec 24, 2025

Merge confidence

43%

incident inc_9f06b8272de54faf · merged by llm · confidence 43%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe an insider incident. Intrusion Nov 1, 2023–Aug 31, 2024. 1 individual reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Not recorded for this incident

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

Sensitive data

identity_government

Incident timeline

Nov 1, 2023breach begins
Dec 24, 2025first dated filing
—watching for filings

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge. 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

  1. NOV 13MD AGMD AG noticefiling day not on record · 1 MD residents—
  2. DEC 24VT AGVT AG noticefirst filing · no count statedday 0
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 1, 2023 – Aug 31, 2024
MD AG
Discovered
—
Data types
Identity (basic) · Government ID · Financial account
MD AG + VT AG
Attack vector
Insider
MD 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
llm
Confidence
0.43 · below the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (43% is the strongest edge).

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

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.