DisclosureLens
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

Numrich Gun Parts Corporation — January 2022 breach

Clustered 9 filings across 9 jurisdictions · filing window Jan 1, 2022 Jun 9, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

45,169

First → last filing

Jan 1, 2022 Jun 9, 2022

Merge confidence

100%

incident inc_530f516ed40d4ce6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Jan 23, 2022–Apr 5, 2022, discovered Mar 28, 2022. 45,169 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 2 more. Notifications rolled out on a 159-day schedule across 9 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
45days

Range of discovered_at dates across filings

Filing span
159days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington WA AG >30dMaine ME AG ≤30d · 25dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Jan 23, 2022breach begins
Mar 28, 2022discovered · members disagree
Jan 1, 2022first filing
Jun 9, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 6CA AGCA AG noticeno count stated+156d
  3. JUN 6OR AGOR AG noticestates nationwide total 45,169+156d
  4. JUN 6MT AGMT AG notice452 MT residents+156d
  5. JUN 6WA AGWA AG notice1,327 WA residents+156d
  6. JUN 6ME AGME AG noticestates nationwide total 45,169+156d
  7. JUN 7MA AGMA AG notice482 MA residents+157d
  8. JUN 7IN AGIN AG noticestates nationwide total 45,169+157d
  9. JUN 9NH AGNH AG noticemost recent · 306 NH residents+159d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 23, 2022Apr 5, 2022
CA AG
Discovered
Mar 28, 2022IL AG + CA AG + MT AG +2May 12, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
CA AG + MT AG + WA AG +3
Attack vector
Unauthorized Access
CA 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)

45,169

Sum of filed state slices

4,092· 9.1% of stated

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

US45,169
WA1,327
IN1,208
MA482
MT452
ME317
NH306

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

159 days

Cadence

~1 / 19.9d

vs. multi-state median

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