DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed16 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 16 records

PATELCO CREDIT UNION — May 2024 breach

Clustered 16 records across 10 jurisdictions: 15 filings and 1 leak-site claim · filing window Aug 20, 2024 → Sep 27, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 records

States

10

Affected · reported

1,009,472

First → last dated filing

Aug 20, 2024 → Sep 27, 2024

Merge confidence

100%

incident inc_12f8a2a18f384e92 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion May 23, 2024–Jun 29, 2024, discovered May 23, 2024. 1,009,472 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 38-day schedule across 13 dated filings beginning Aug 20, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
83days

Range of discovered_at dates across filings

Filing span
38days

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 clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 52dWashington⏱ WA AG >30dLeak gap⏱ Leak >30dCalifornia✓ CA 60-day OK · 46dDate basis✓ Clock withheld · confirmation dateMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 23, 2024breach begins
May 23, 2024discovered · members disagree
Aug 20, 2024first dated filing
Sep 27, 2024most 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. JUN 29Leak siteransomhub postfirst record · attacker claim · unverifiedday 0
  2. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  3. AUG 20ME AGME AG noticestates nationwide total 726,000+52d
  4. AUG 20IN AGIN AG noticestates nationwide total 1,009,472+52d
  5. AUG 20MT AGMT AG notice557 MT residents+52d
  6. AUG 20WA AGWA AG notice4,286 WA residents+52d
  7. AUG 20CA AGCA AG noticeno count stated+52d
  8. AUG 20OR AGOR AG noticestates nationwide total 726,000+52d
  9. AUG 21MA AGMA AG notice1,829 MA residents+53d
  10. AUG 21VT AGVT AG noticeno count stated+53d
  11. AUG 26NH AGNH AG notice96 NH residents+58d
  12. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  13. SEP 23ME AGME AG noticestates nationwide total 1,009,472+86d
  14. SEP 23VT AGVT AG noticeno count stated+86d
  15. SEP 23WA AGWA AG notice8,176 WA residents+86d
  16. SEP 27NH AGNH AG noticemost recent · 33 NH residents+90d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 23, 2024 – Jun 29, 2024
ME AG
Discovered
May 23, 2024IL AGJun 29, 2024IL AG + ME AG + MT AG +4Aug 14, 2024OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
ME AG + MT AG + WA AG +4
Attack vector
Ransomware
ME 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)

1,009,472

Sum of filed state slices

12,330· 1.2% of stated

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

US1,009,472
WA8,176
MA1,829
IN1,403
MT557
ME269
NH96

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 filing15 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
deterministic
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

38 days

Cadence

~1 / 3.2d

vs. multi-state median

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