All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 5 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 5 filings

Bombas — September 2013 breach

Clustered 5 filings across 5 jurisdictions · filing window May 18, 2018 → May 21, 2018. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

41,000

First → last filing

May 18, 2018 → May 21, 2018

Merge confidence

100%

incident inc_f04b4c679a3a4972 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe malware. Intrusion Sep 1, 2013–Feb 9, 2015, discovered Jan 15, 2015 — the first regulatory filing landed 1219 days later (flagged late). 41,000 individuals reported across the linked filings. Data reported: PII, Financial account, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

1219days

Discovered → first regulatory filing

Discovery variance

1082days

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 clocksCalifornia✗ CA 60-day late · 1317dFull 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.