City of Philadelphia — March 2020 breach

Clustered 2 filings across 2 jurisdictions · filing window Apr 14, 2021 → Jun 11, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

49,255

First → last filing

Apr 14, 2021 → Jun 11, 2021

Merge confidence

100%

incident inc_060ceb0b7fd54c81 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. Intrusion Mar 11, 2020–Nov 16, 2020, discovered Mar 31, 2020 — the first regulatory filing landed 379 days later. 49,255 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

379days

Discovered → first regulatory filing

Discovery variance

413days

Range of discovered_at dates across filings

Filing span

58days

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 clocksMaine✓ ME AG ≤30d · 24dFull 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.