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

FIDELITY NATIONAL INFORMATION SERVICES, INC. — April 2023 breach

Clustered 24 records across 6 jurisdictions: 23 filings and 1 leak-site claim · filing window Jun 21, 2023 → Nov 20, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

24 records

States

6

Affected · reported

793,626

First → last dated filing

Jun 21, 2023 → Nov 20, 2023

Merge confidence

100%

incident inc_616da0ec33844053 · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 96 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 23 regulatory filings and 1 unverified claim. The filings describe a third-party compromise. Intrusion Apr 3, 2023–Jul 30, 2023, discovered May 31, 2023. 793,626 individuals reported across the linked filings. Data reported: Government ID, PCI, Financial account, and 2 more. Notifications rolled out on a 152-day schedule across 21 dated filings beginning Jun 21, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
54days

Range of discovered_at dates across filings

Filing span
152days

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 clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dLeak gap⏱ Leak >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 3, 2023breach begins
May 31, 2023discovered · members disagree
Jun 21, 2023first dated filing
Nov 20, 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. JUN 21MA AGMA AG noticefirst filing · 167 MA residentsday 0
  4. JUN 26MA AGMA AG notice301 MA residents+5d
  5. JUN 30Leak sitecl0p postattacker claim · unverified+9d
  6. JUL 17MA AGMA AG notice5 MA residents+26d
  7. JUL 17MT AGMT AG notice33 MT residents+26d
  8. JUL 17WA AGWA AG notice13,795 WA residents+26d
  9. JUL 21MT AGMT AG notice8 MT residents+30d
  10. JUL 21MA AGMA AG notice338 MA residents+30d
  11. AUG 8MT AGMT AG notice8 MT residents+48d
  12. AUG 10MT AGMT AG notice756 MT residents+50d
  13. AUG 11OR AGOR AG noticestates nationwide total 429,252+51d
  14. SEP 8MA AGMA AG notice10 MA residents+79d
  15. SEP 19MA AGMA AG notice2 MA residents+90d
  16. SEP 19MA AGMA AG notice383 MA residents+90d
  17. SEP 28MT AGMT AG notice1 MT residents+99d
  18. OCT 4OR AGOR AG noticestates nationwide total 793,626+105d
  19. OCT 4CA AGCA AG noticeno count stated+105d
  20. OCT 4MA AGMA AG notice10,070 MA residents+105d
  21. OCT 6MA AGMA AG notice71 MA residents+107d
  22. NOV 9CA AGCA AG noticeno count stated+141d
  23. NOV 9MA AGMA AG notice168 MA residents+141d
  24. NOV 20MA AGMA AG noticemost recent · 1,417 MA residents+152d
  25. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 3, 2023 – May 31, 2023
MT AG
Discovered
May 31, 2023IL AG + OR AG + CA AGJun 1, 2023MT AGJun 13, 2023MT AG + WA AGJun 21, 2023MT AGJul 12, 2023OR AG + CA AGJul 24, 2023MT AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
MA AG + MT AG + WA AG +1
Attack vector
Third-Party / Supply Chain· CL0P
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)

793,626

Sum of filed state slices

24,621· 3.1% of stated

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

US793,626
WA13,795
MA10,070
MT756

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 filing23 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 Aug 25, 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

152 days

Cadence

~1 / 7.6d

vs. multi-state median

30.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.