DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed4 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Alpha Industries, Inc. — July 2017 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

2

Affected · reported

1,500

First → last filing

Oct 2, 2017 → Nov 1, 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. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. 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. Data reported: PCI, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 30-day schedule across 4 filings beginning Oct 2, 2017. 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
30days

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
Nov 1, 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

  1. OCT 2MA AGMA AG noticefirst filing · 11 MA residentsday 0
  2. OCT 2NH AGNH AG noticestates nationwide total 634day 0
  3. OCT 26NH AGNH AG noticestates nationwide total 1,500+24d
  4. NOV 1MA AGMA AG noticemost recent · 10 MA residents+30d
  5. 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
NH AG
Discovered
Aug 25, 2017· 50d undetected
NH AG
Data types
Financial account · Financial credentials · Identity (basic) · PCI
MA AG + NH AG
Attack vector
Third-Party / Supply Chain
NH AG

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

17· 1.1% of stated

99% 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 filing4 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

30 days

Cadence

~1 / 10d

vs. multi-state median

6.0× 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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.