Confirmed breach. Intrusion Oct 23, 2025, discovered Oct 27, 2025 — the first regulatory filing landed 77 days later. 1 individuals reported across the linked filings.
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.
Regulatory clocksMaine⏱ ME AG >30d · 77dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1
Data types
—
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 23, 2025
When the intrusion reportedly occurred, per the linked filings
JPMorgan Chase Bank, N.A. reported a data breach to the Maine Attorney General, which was classified as an external system breach or hacking incident. The breach was discovered on October 27, 2025, and affected one Maine resident. The company offered 24 months of credit monitoring services to the individual affected.
Affected (this filing): 1
ME AG >30d · 77dME resident >60d · 74d
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.