Aptos — February 2016 breach

Clustered 6 filings across 4 jurisdictions · filing window Feb 25, 2017 → Mar 24, 2017. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

66,987

First → last filing

Feb 25, 2017 → Mar 24, 2017

Merge confidence

100%

incident inc_075f5223db294480 · merged by deterministic · confidence 100%

Part of the Aptos supply-chain incident (2017) — at least 12 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Feb 1, 2016–Dec 31, 2016, discovered Nov 1, 2016 — the first regulatory filing landed 116 days later (flagged late). 66,987 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Notifications rolled out on a 27-day schedule across 6 filings beginning Feb 25, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

116days

Discovered → first regulatory filing

Discovery variance

14days

Range of discovered_at dates across filings

Filing span

27days

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 · 112dOregon✗ OR AG >45dFull 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.