State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 4 filings
Net32, Inc. — September 2018 breach
Clustered 4 filings across 4 jurisdictions · filed Oct 25, 2018. View entity profile → Other incidents for this victim →
⚠ 2 cross-filing discrepancies →Merge100%
incident inc_bc2089594c904fa6 · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. Intrusion Sep 22, 2018–Sep 25, 2018, discovered Sep 22, 2018 — the first regulatory filing landed 33 days later. 390 individuals reported across the linked filings. Data reported: Financial account, Identity (basic), and PCI. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
Notification delay
33days
Discovered → first regulatory filing
Discovery variance
3days
Range of discovered_at dates across filings
Filing span
0days
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 OK · 5dFull clock table in Litigation Timeline
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.