DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 10 records

SNAP-ON INCORPORATED — March 2022 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Apr 7, 2022 → Apr 20, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

41,052

First → last dated filing

Apr 7, 2022 → Apr 20, 2022

Merge confidence

100%

incident inc_f8b61aad1bf64ac2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 1, 2022–Mar 3, 2022, discovered Mar 1, 2022. 41,052 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 4 more. Notifications rolled out on a 13-day schedule across 8 dated filings beginning Apr 7, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
6days

Range of discovered_at dates across filings

Filing span
13days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dMaine⏱ ME AG >30d · 31dCalifornia✓ CA 60-day OK · 37dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2022breach begins
Mar 1, 2022discovered · members disagree
Apr 7, 2022first dated filing
Apr 20, 2022most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. APR 7IN AGIN AG noticefirst filing · states nationwide total 41,052day 0
  3. APR 7ME AGME AG noticestates nationwide total 41,052day 0
  4. APR 7CA AGCA AG noticeno count statedday 0
  5. APR 7MT AGMT AG notice144 MT residentsday 0
  6. APR 8NH AGNH AG notice226 NH residents+1d
  7. APR 10Leak siteconti postattacker claim · unverified+3d
  8. APR 13MA AGMA AG notice673 MA residents+6d
  9. APR 14WA AGWA AG notice531 WA residents+7d
  10. APR 20OR AGOR AG noticemost recent · no count stated+13d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 3, 2022
IN AG
Discovered
Mar 1, 2022CA AG + MT AG + NH AG +1Mar 3, 2022IL AG + OR AGMar 7, 2022ME AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + CA AG + MT AG +3
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)

41,052

Sum of filed state slices

2,669· 6.5% of stated

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

US41,052
IN775
MA673
WA531
ME320
NH226
MT144

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

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 Aug 23, 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

13 days

Cadence

~1 / 1.9d

vs. multi-state median

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