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

JPMorgan Chase Bank, National Association — August 2021 breach

Clustered 12 filings across 9 jurisdictions · filing window Apr 15, 2024 → May 31, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

451,809

First → last filing

Apr 15, 2024 → May 31, 2024

Merge confidence

100%

incident inc_3be3d61e0d0542b3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Aug 26, 2021–Feb 26, 2024, discovered Feb 26, 2024 — the first regulatory filing landed 49 days later; 2 later filings were flagged late. 451,809 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 46-day schedule across 12 filings beginning Apr 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
49days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
46days

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 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 63dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2021breach begins
Feb 26, 2024discovered
notification delay · 49 days
Apr 15, 2024first filing
May 31, 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 15MA AGMA AG noticefirst filing · 1 MA residentsday 0
  2. APR 18IN AGIN AG noticestates nationwide total 451,809+3d
  3. APR 18DE AGDE AG noticeno count stated+3d
  4. APR 18VT AGVT AG noticeno count stated+3d
  5. APR 18WA AGWA AG notice4,513 WA residents+3d
  6. APR 27CA AGCA AG noticeno count stated+12d
  7. APR 28OR AGOR AG noticestates nationwide total 451,809+13d
  8. APR 29CA AGCA AG noticeno count stated+14d
  9. APR 29ME AGME AG noticestates nationwide total 451,809+14d
  10. MAY 2OR AGOR AG noticestates nationwide total 451,809+17d
  11. MAY 6MT AGMT AG notice689 MT residents+21d
  12. MAY 31MA AGMA AG noticemost recent · 1 MA residents+46d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2021
IN AG
Discovered
Feb 26, 2024· 914d undetected
DE AG + VT AG + WA AG +4
Data types
Financial · Financial account · Identity (basic) · Government ID
MA AG + DE AG + VT AG +4
Attack vector
Unauthorized Access
DE 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

20,145· 4.5% of stated

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

US451,809
IN13,259
WA4,513
ME1,683
MT689
MA1

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 filing12 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 11, 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

46 days

Cadence

~1 / 4.2d

vs. multi-state median

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