DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 12 records

Financial Institution Service Corporation — May 2023 breach

Clustered 12 records across 9 jurisdictions: 11 filings and 1 leak-site claim · filing window Sep 22, 2023 → Sep 29, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

9

Affected · reported

753,261

First → last dated filing

Sep 22, 2023 → Sep 29, 2023

Merge confidence

100%

incident inc_c78aca6737bf4341 · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 89 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 30, 2023–May 31, 2023, discovered May 21, 2023. 753,261 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 7-day schedule across 9 dated filings beginning Sep 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
10days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dOregon✗ OR AG >45dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 114dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 30, 2023breach begins
May 21, 2023discovered · members disagree
Sep 22, 2023first dated filing
Sep 29, 2023most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 7Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  4. SEP 22WA AGWA AG notice2,140 WA residents+77d
  5. SEP 22CA AGCA AG noticeno count stated+77d
  6. SEP 22MT AGMT AG notice272 MT residents+77d
  7. SEP 22IN AGIN AG noticestates nationwide total 753,261+77d
  8. SEP 22ME AGME AG noticestates nationwide total 753,261+77d
  9. SEP 22OR AGOR AG noticestates nationwide total 753,261+77d
  10. SEP 22MA AGMA AG notice258 MA residents+77d
  11. SEP 28ME AGME AG noticestates nationwide total 353,309+83d
  12. SEP 29SC AGSC AG noticemost recent · 9,870 SC residents+84d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023 – May 31, 2023
WA AG
Discovered
May 21, 2023IL AGMay 30, 2023IL AGMay 31, 2023WA AG + MT AG + ME AG +2filings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI
WA AG + CA AG + MT AG +3
Attack vector
Unauthorized Access
WA 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)

753,261

Sum of filed state slices

21,167· 2.8% of stated

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

US753,261
SC9,870
IN8,530
WA2,140
MT272
MA258
ME97

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

7 days

Cadence

~1 / 0.9d

vs. multi-state median

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