Clustered 2 filings across 2 jurisdictions · filing window Apr 18, 2024 → Apr 29, 2024. View entity profile → Other incidents for this victim →
incident inc_3440c949cbda4044 · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
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.
CA DE
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 26, 2021 → Feb 23, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 26, 2024
Reported by DELAWARE AG, CALIFORNIA AG filings
J.P. Morgan Chase Bank, N.A. disclosed a data breach affecting plan participants of {{PlanClientName}}. Between August 26, 2021, and February 23, 2024, three authorized system users accessed reports containing names, addresses, SSNs, and bank account numbers. The incident was discovered on February 26, 2024, and remediated via a software update. Affected individuals were offered two years of credit monitoring.
JPMorgan Chase Bank, N.A. disclosed a software issue causing unauthorized access to plan participant data. Between August 26, 2021, and February 23, 2024, three authorized users accessed reports containing names, addresses, SSNs, and bank account details. The issue was discovered on February 26, 2024, and promptly addressed with a software update. Affected individuals are offered two years of credit monitoring.
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.