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

Alta Forest Products LLC — August 2022 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

2

Affected · reported

2,100

First → last filing

Oct 31, 2022 → Nov 1, 2022

Merge confidence

100%

incident inc_3b9e1160e35e49d3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion Aug 17, 2022–Aug 31, 2022, discovered Sep 1, 2022 — the first regulatory filing landed 60 days later. 2,100 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

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 clocksWashington⏱ WA AG >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 17, 2022breach begins
Sep 1, 2022discovered
notification delay · 60 days
Oct 31, 2022first filing
Nov 1, 2022most 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 31HHS OCRHHS OCR noticefirst filing · states nationwide total 2,100day 0
  2. OCT 31MT AGMT AG notice34 MT residentsday 0
  3. NOV 1WA AGWA AG noticemost recent · 1,635 WA residents+1d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 17, 2022 – Aug 31, 2022
MT AG
Discovered
Sep 1, 2022· 15d undetected
MT AG + WA AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MT AG + WA AG
Attack vector
Unauthorized Access
HHS OCR

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)

2,100

Sum of filed state slices

1,669· 79.5% of stated

21% 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 filing3 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

1 days

Cadence

~1 / 0.5d

vs. multi-state median

6.0× faster

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.