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

Pathward, N.A. — September 2022 breach

Clustered 9 filings across 9 jurisdictions · filing window Oct 31, 2022 → Nov 1, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

165,727

First → last filing

Oct 31, 2022 → Nov 1, 2022

Merge confidence

100%

incident inc_2a631b65371d45f9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Sep 4, 2022–Sep 12, 2022, discovered Sep 11, 2022 — the first regulatory filing landed 50 days later (flagged late). 165,727 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
50days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

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 >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 51dSouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 50dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Sep 4, 2022breach begins
Sep 11, 2022discovered
notification delay · 50 days
Oct 31, 2022first filing
Nov 1, 2022most 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. OCT 31MT AGMT AG noticefirst filing · 398 MT residentsday 0
  2. OCT 31DE AGDE AG noticeno count statedday 0
  3. OCT 31IN AGIN AG noticestates nationwide total 165,727day 0
  4. NOV 1WA AGWA AG notice2,639 WA residents+1d
  5. NOV 1SC AGSC AG notice1,679 SC residents+1d
  6. NOV 1CA AGCA AG noticeno count stated+1d
  7. NOV 1ME AGME AG noticestates nationwide total 165,727+1d
  8. NOV 1MA AGMA AG notice4,270 MA residents+1d
  9. NOV 1OR AGOR AG noticemost recent · states nationwide total 165,727+1d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 4, 2022 – Sep 12, 2022
MT AG
Discovered
Sep 11, 2022· 7d undetected
MT AG + DE AG + WA AG +4
Data types
Financial account · Financial credentials · Identity (basic) · PII
MT AG + DE AG + WA AG +4
Attack vector
Unauthorized Access
MT 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)

165,727

Sum of filed state slices

12,590· 7.6% of stated

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

US165,727
MA4,270
IN2,913
WA2,639
SC1,679
ME691
MT398

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 filing9 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
Reviewed
operator-reviewed Jun 12, 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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

8.0× faster

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.