PAX Labs, Inc. — June 2016 breach

Clustered 4 filings across 4 jurisdictions · filing window Aug 11, 2016 → Aug 12, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

6,000

First → last filing

Aug 11, 2016 → Aug 12, 2016

Merge confidence

100%

incident inc_94d9e683d53a4faa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Jun 25, 2016–Jul 22, 2016, discovered Jul 15, 2016 — the first regulatory filing landed 27 days later. 6,000 individuals reported across the linked filings. Data reported: PCI, Financial account, Financial credentials, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

1days

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 · 28dFull 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.