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

STURM, RUGER & COMPANY, INC. — September 2020 breach

Clustered 9 filings across 8 jurisdictions · filing window Aug 2, 2022 → Aug 19, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

167,963

First → last filing

Aug 2, 2022 → Aug 19, 2022

Merge confidence

100%

incident inc_5a66f603763c4460 · merged by deterministic · confidence 100%

Part of the FreeStyle Solutions supply-chain incident (2022) — at least 12 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe malware. Intrusion Sep 18, 2020–Feb 3, 2022, discovered Aug 2, 2022. 167,963 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, Identity (basic), and 3 more. Notifications rolled out on a 17-day schedule across 9 filings beginning Aug 2, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
0days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
17days

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 OK · 16dMaine✓ ME AG ≤30d · 15dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Sep 18, 2020breach begins
Aug 2, 2022discovered
notification delay · 0 days
Aug 2, 2022first filing
Aug 19, 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. AUG 2DE AGDE AG noticefirst filing · no count statedday 0
  2. AUG 17DE AGDE AG noticestates nationwide total 167,963+15d
  3. AUG 17CA AGCA AG noticeno count stated+15d
  4. AUG 17ME AGME AG noticestates nationwide total 167,963+15d
  5. AUG 17OR AGOR AG noticestates nationwide total 167,963+15d
  6. AUG 18IN AGIN AG noticestates nationwide total 167,963+16d
  7. AUG 18MA AGMA AG notice2,179 MA residents+16d
  8. AUG 18WA AGWA AG notice4,866 WA residents+16d
  9. AUG 19NH AGNH AG noticemost recent · 1,639 NH residents+17d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 18, 2020 – Feb 3, 2022
DE AG
Discovered
Aug 2, 2022· 683d undetected
DE AG + CA AG + ME AG +2
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI · PII
DE AG + CA AG + ME AG +3
Attack vector
Third-Party / Supply Chain
DE 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)

167,963

Sum of filed state slices

14,813· 8.8% of stated

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

US167,963
WA4,866
IN4,385
MA2,179
NH1,639
ME1,176
DE568

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing9 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

17 days

Cadence

~1 / 2.1d

vs. multi-state median

2.1× 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.