DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddispossessorhigh sensitivity
Merged incident · 7 filings

Quorum Federal Credit Union — May 2023 breach

Clustered 7 filings across 6 jurisdictions · filing window Jul 5, 2023 → Oct 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

17,054

First → last filing

Jul 5, 2023 → Oct 18, 2023

Merge confidence

100%

incident inc_95341b2b35a54752 · merged by human · 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: 5 regulatory filings and 2 unverified claims. The filings describe hacking. Intrusion May 28, 2023–May 31, 2023, discovered May 31, 2023 — the first regulatory filing landed 47 days later. 17,054 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 Jul 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
47days

Discovered → first regulatory filing

Discovery variance
20days

Range of discovered_at dates across filings

Leak precedence
12days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
105days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✓ ME AG ≤30d · 27dMassachusetts✓ MA credit monitoring dueWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 47 days
Jul 17, 2023first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 5Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. JUL 17CA AGCA AG noticeno count stated+12d
  3. JUL 17MT AGMT AG notice13 MT residents+12d
  4. JUL 17ME AGME AG noticestates nationwide total 17,054+12d
  5. JUL 17MA AGMA AG notice121 MA residents+12d
  6. JUL 17WA AGWA AG notice802 WA residents+12d
  7. OCT 18Leak sitedispossessor postmost recent · attacker claim · unverified+105d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023 – May 31, 2023
CA AG
Discovered
May 31, 2023MT AGJun 20, 2023ME AG + WA AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + MT AG + WA AG +2
Attack vector
Third-Party / Supply Chain
CA 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)

17,054

Sum of filed state slices

959· 5.6% of stated

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

US17,054
WA802
MA121
ME23
MT13

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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 23, 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

105 days

Cadence

~1 / 17.5d

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.