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

Wilson's Gun Shop, Inc. — September 2020 breach

Clustered 9 filings across 9 jurisdictions · filing window Sep 7, 2022 → Sep 12, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

113,497

First → last filing

Sep 7, 2022 → Sep 12, 2022

Merge confidence

100%

incident inc_27040cb3e6564053 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Sep 17, 2020–Feb 3, 2022, discovered Jul 26, 2022 — the first regulatory filing landed 43 days later. 113,497 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 2 more. Notifications rolled out on a 5-day schedule across 9 filings beginning Sep 7, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
43days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
5days

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 clocksMaine⏱ ME AG >30d · 43dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Sep 17, 2020breach begins
Jul 26, 2022discovered
notification delay · 43 days
Sep 7, 2022first filing
Sep 12, 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. SEP 7ME AGME AG noticefirst filing · states nationwide total 113,497day 0
  2. SEP 7MT AGMT AG notice778 MT residentsday 0
  3. SEP 7OR AGOR AG noticestates nationwide total 113,497day 0
  4. SEP 7SC AGSC AG notice1,906 SC residentsday 0
  5. SEP 8IN AGIN AG noticestates nationwide total 113,000+1d
  6. SEP 8MA AGMA AG notice1,413 MA residents+1d
  7. SEP 8CA AGCA AG noticeno count stated+1d
  8. SEP 12WA AGWA AG notice3,788 WA residents+5d
  9. SEP 12NH AGNH AG noticemost recent · 826 NH residents+5d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2020
ME AG
Discovered
Jul 26, 2022· 677d undetected
ME AG + OR AG + WA AG +1
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
ME AG + MT AG + SC AG +4
Attack vector
Unauthorized Access
ME 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)

113,497

Sum of filed state slices

11,938· 10.5% of stated

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

US113,497
WA3,788
IN2,723
SC1,906
MA1,413
NH826
MT778
ME504

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-confirmed · 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

5 days

Cadence

~1 / 0.6d

vs. multi-state median

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