All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed10 filings · 9 statesUnverified claimConfirmedEnforcedcontihigh sensitivity

Merged incident · 10 filings

SNAP-ON INCORPORATED — March 2022 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

41,052

First → last filing

Jan 1, 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 109-day schedule across 9 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

6days

Range of discovered_at dates across filings

Leak precedence

Noneclaim trailed by 99d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

109days

Time between earliest and latest filing

Not recorded for this incident

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

Jan 1, 2022first filing

Apr 20, 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

JAN 1IL AGIL AG noticefirst filing · no count statedday 0
APR 7IN AGIN AG noticestates nationwide total 41,052auto-linked+96d
APR 7ME AGME AG noticestates nationwide total 41,052auto-linked+96d
APR 7CA AGCA AG noticeno count statedauto-linked+96d
APR 7MT AGMT AG notice144 MT residentsauto-linked+96d
APR 8NH AGNH AG notice226 NH residentsauto-linked+97d
APR 10Leak siteconti postattacker claim · unverifiedoperator-confirmed+99d
APR 13MA AGMA AG notice673 MA residentsauto-linked+102d
APR 14WA AGWA AG notice531 WA residentsauto-linked+103d
APR 20OR AGOR AG noticemost recent · no count statedauto-linked+109d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 3, 2022
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
Attack vector: Unauthorized Access

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

109 days

Cadence

~1 / 12.1d

vs. multi-state median

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