InFirst Bank — October 2020 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 4, 2020 → Dec 30, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

36,404

First → last filing

Dec 4, 2020 → Dec 30, 2020

Merge confidence

100%

incident inc_9edc98380cb948a7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Oct 22, 2020, discovered Oct 22, 2020 — the first regulatory filing landed 43 days later. 36,404 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 26-day schedule across 5 filings beginning Dec 4, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

43days

Discovered → first regulatory filing

Discovery variance

25days

Range of discovered_at dates across filings

Filing span

26days

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 · 32dMassachusetts✓ 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.