Jewish Federation of Greater Pittsburgh — November 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Sep 19, 2025 → Sep 22, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

14,677

First → last filing

Sep 19, 2025 → Sep 22, 2025

Merge confidence

100%

incident inc_27f13292b86345ee · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Nov 5, 2024–Nov 12, 2024, discovered Nov 12, 2024 — the first regulatory filing landed 311 days later (flagged late). 14,677 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

311days

Discovered → first regulatory filing

Discovery variance

281days

Range of discovered_at dates across filings

Filing span

3days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine✓ ME AG ≤30d · 30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.