City of Philadelphia — March 2020 breach

One linked filing — more sources may join as they report · filed Aug 6, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

Affected · reported

108,214

First → last filing

Aug 6, 2021

incident inc_8e4872e4ffc64221 · merged by deterministic

Confirmed breach. The filing describes unauthorized access. Intrusion Mar 11, 2020, discovered Jul 12, 2021 — the first regulatory filing landed 25 days later. 108,214 individuals reported across the linked filings. Data reported: Government ID.

Litigation Timing

Notification delay

25days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine✓ ME AG ≤30d · 25dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 11, 2020breach begins

Jul 12, 2021discovered

notification delay · 25 days

Aug 6, 2021first & only 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

AUG 6ME AGME AG noticeonly filing · states nationwide total 108,214day 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 11, 2020
Discovered: Jul 12, 2021· 488d undetected
Data types: Government ID
Attack vector: Unauthorized Access

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)

108,214

Sum of filed state slices

4· 0.0% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.