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

Flagstar Bank, National Association — May 2023 breach

Clustered 15 filings across 9 jurisdictions · filing window Oct 5, 2023 → Dec 27, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

9

Affected · reported

838,073

First → last filing

Oct 5, 2023 → Dec 27, 2023

Merge confidence

100%

incident inc_f6f7b87c91554789 · merged by deterministic · confidence 100%

Part of the FISERV, INC. supply-chain incident (2023) — at least 10 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe hacking. Intrusion May 27, 2023–May 31, 2023, discovered Jun 3, 2023 — the first regulatory filing landed 124 days later (flagged late). 838,073 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 83-day schedule across 15 filings beginning Oct 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
124days

Discovered → first regulatory filing

Discovery variance
151days

Range of discovered_at dates across filings

Filing span
83days

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 clocksMaine✗ ME AG >90d · 124dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
Jun 3, 2023discovered · members disagree
notification delay · 124 days
Oct 5, 2023first filing
Dec 27, 2023most 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 5MA AGMA AG noticefirst filing · 1,369 MA residentsday 0
  2. OCT 5ME AGME AG noticestates nationwide total 837,390day 0
  3. OCT 5VT AGVT AG noticeno count statedday 0
  4. OCT 5NH AGNH AG notice278 NH residentsday 0
  5. OCT 5MT AGMT AG notice304 MT residentsday 0
  6. OCT 5CA AGCA AG noticeno count statedday 0
  7. OCT 5WA AGWA AG notice2,412 WA residentsday 0
  8. OCT 6IN AGIN AG noticestates nationwide total 837,390+1d
  9. OCT 6OR AGOR AG noticestates nationwide total 837,390+1d
  10. NOV 5MA AGMA AG notice48 MA residents+31d
  11. NOV 5ME AGME AG noticestates nationwide total 11,833+31d
  12. NOV 6NH AGNH AG notice6 NH residents+32d
  13. DEC 15CA AGCA AG noticeno count stated+71d
  14. DEC 27ME AGME AG noticestates nationwide total 25,891+83d
  15. DEC 27ME AGME AG noticemost recent · states nationwide total 838,073+83d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023 – May 31, 2023
ME AG
Discovered
Jun 3, 2023ME AGAug 3, 2023WA AGAug 8, 2023ME AGNov 1, 2023NH AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + NH AG +4
Attack vector
Unauthorized Access
ME 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)

838,073

Sum of filed state slices

90,783· 10.8% of stated

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

US838,073
IN86,243
WA2,412
MA1,369
MT304
NH278
ME177

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

83 days

Cadence

~1 / 5.9d

vs. multi-state median

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