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

SouthState Bank, National Association — February 2024 breach

Clustered 5 filings across 4 jurisdictions · filing window Feb 9, 2024 → May 24, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

844,672

First → last filing

Feb 9, 2024 → May 24, 2024

Merge confidence

100%

incident inc_c7406bd59f754f66 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filing describes unauthorized access. Intrusion Feb 7, 2024, discovered Feb 6, 2024 — the first regulatory filing landed 3 days later (flagged late). 844,672 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 105-day schedule across 5 filings beginning Feb 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
3days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Materiality delta
3days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
105days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksSEC✗ SEC 4-day late · 52dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 7, 2024breach begins
Feb 6, 2024discovered · members disagree
notification delay · 3 days
Feb 9, 2024first filing
May 24, 2024most 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. FEB 9SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. MAR 1IL AGIL AG noticeno count stated+21d
  3. MAR 29SEC 8-KSEC 8-K noticeno count stated+49d
  4. MAR 29CA AGCA AG noticeno count stated+49d
  5. MAY 24SC AGSC AG noticemost recent · 844,672 SC residents+105d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 7, 2024
CA AG
Discovered
Feb 6, 2024SEC 8-KFeb 7, 2024IL AG + SC AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
SEC 8-K + CA AG + SC AG
Attack vector
Unauthorized Access
SC AG

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

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

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

SEC 8-K / victim statement2 members

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

105 days

Cadence

~1 / 26.3d

vs. multi-state median

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