DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Sunflower Bank, National Association — May 2023 breach

Clustered 8 filings across 6 jurisdictions · filing window Jul 14, 2023 → Oct 4, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

316

First → last filing

Jul 14, 2023 → Oct 4, 2023

Merge confidence

100%

incident inc_c9d85968db7e4aa1 · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion May 27, 2023, discovered May 31, 2023 — the first regulatory filing landed 44 days later (flagged late). 316 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 82-day schedule across 8 filings beginning Jul 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
44days

Discovered → first regulatory filing

Discovery variance
75days

Range of discovered_at dates across filings

Filing span
82days

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.

Regulatory clocksCalifornia✗ CA 60-day late · 119dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 44 days
Jul 14, 2023first filing
Oct 4, 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. JUL 14SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. AUG 14IN AGIN AG notice132 IN residents+31d
  3. AUG 15NH AGNH AG notice23 NH residents+32d
  4. AUG 15CA AGCA AG noticeno count stated+32d
  5. AUG 15MT AGMT AG notice86 MT residents+32d
  6. AUG 22MA AGMA AG notice75 MA residents+39d
  7. OCT 2NH AGNH AG notice23 NH residents+80d
  8. OCT 4CA AGCA AG noticemost recent · no count stated+82d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023
IN AG
Discovered
May 31, 2023SEC 8-K + NH AG + MT AG +1Aug 14, 2023NH AGfilings disagree on discovery
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
SEC 8-K + NH AG + CA AG +2
Attack vector
Unauthorized Access
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

IN132
MT86
MA75
NH23

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

82 days

Cadence

~1 / 11.7d

vs. multi-state median

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