All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Alpha Industries, Inc. — July 2017 breach

Clustered 2 filings across 1 jurisdiction · filing window Oct 2, 2017 → Oct 26, 2017. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

1,500

First → last filing

Oct 2, 2017 → Oct 26, 2017

Merge confidence

100%

incident inc_119155eb37e54f9a · 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. One breach, 2 legal records. Intrusion Jul 6, 2017–Aug 9, 2017, discovered Aug 25, 2017 — the first regulatory filing landed 38 days later. 1,500 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

38days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

24days

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.

Sensitive data

financial_credentials

Incident timeline

Jul 6, 2017breach begins

Aug 25, 2017discovered

notification delay · 38 days

Oct 2, 2017first filing

Oct 26, 2017most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

OCT 2NH AGNH AG noticefirst filing · states nationwide total 634day 0
OCT 26NH AGNH AG noticemost recent · states nationwide total 1,500+24d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jul 6, 2017 – Aug 9, 2017
Discovered: Aug 25, 2017· 50d undetected
Data types: Identity (basic) · Financial account · Financial credentials
Attack vector: Third-Party / Supply Chain
Response: Engaged a leading cybersecurity firm to determine the scope of the matter · Removed the malicious code · Disabled the page used to gain access to its system

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,500

Sum of filed state slices

6· 0.4% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

24 days

vs. multi-state median

4.8× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.