DisclosureLens
UnknownInformationLow

Aptos

bd_95597eac1553f536 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 15, 2016

Filed

Mar 24, 2017

To disclose

18 weeks

Affected

Not disclosed

Linked

6 filings

Confidence

95%
Full breach record for Aptos →

Aptos, Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2017-03-24. The breach occurred during 2/1/2016 - 12/31/2016. The breach was discovered on 11/15/2016.

Oregon clock✗ OR AG >45d18 weeks discovery → filing
⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 288 days
discovery → filing · 18 weeks / 129 days

Feb 1, 2016

Begins

Nov 15, 2016

Discovered

Mar 24, 2017

Filed

This filing is one of 6 filings about the same incident.View merged incident
Part of Aptos supply-chain incident (2017) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Show 1 more filing ↓up to 27d gap

Filing propagation · 6 filings · 4 states

View merged incident ↗
New Hampshire State AGFeb 25 · first
California State AGFeb 25 · first
Massachusetts State AG+2d
California State AG+2d
New Hampshire State AG+6d
Oregon State AG+27d · this page

Pattern: first filing Feb 25 (NH), last Mar 24 (OR) — a 27-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.