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

J.P. Morgan — August 2021 breach

Clustered 5 filings across 5 jurisdictions · filing window Apr 18, 2024 → May 6, 2024. View entity profile → Other incidents for this victim →

✓ affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

451,809

First → last filing

Apr 18, 2024 → May 6, 2024

Merge confidence

100%

incident inc_b61cb413c8af470d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Aug 26, 2021–Feb 26, 2024, discovered Feb 26, 2024 — the first regulatory filing landed 52 days later (flagged late). 451,809 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 18-day schedule across 5 filings beginning Apr 18, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
52days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
18days

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 clocksOregon✗ OR AG >45dVermont⏱ VT AG >14 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2021breach begins
Feb 26, 2024discovered
notification delay · 52 days
Apr 18, 2024first filing
May 6, 2024most 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. APR 18VT AGVT AG noticefirst filing · no count statedday 0
  2. APR 18DE AGDE AG noticeno count statedday 0
  3. APR 27CA AGCA AG noticeno count stated+9d
  4. APR 28OR AGOR AG noticestates nationwide total 451,809+10d
  5. MAY 6MT AGMT AG noticemost recent · 689 MT residents+18d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2021 – Feb 23, 2024
VT AG
Discovered
Feb 26, 2024· 914d undetected
VT AG + DE AG + CA AG +2
Data types
Identity (basic) · Government ID · Financial account
VT AG + DE AG + CA AG +1
Attack vector
Unauthorized Access
VT AG

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)

451,809

Sum of filed state slices

689· 0.2% of stated

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

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

18 days

Cadence

~1 / 4.5d

vs. multi-state median

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