DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

L. KNIFE & SON, LLC — October 2022 breach

Clustered 7 filings across 6 jurisdictions · filing window Dec 23, 2022 → Jan 30, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

14,337

First → last filing

Dec 23, 2022 → Jan 30, 2023

Merge confidence

100%

incident inc_69f00432967c4aaf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Oct 13, 2022–Oct 19, 2022, discovered Nov 1, 2022 — the first regulatory filing landed 52 days later. 14,337 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 38-day schedule across 7 filings beginning Dec 23, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
52days

Discovered → first regulatory filing

Discovery variance
37days

Range of discovered_at dates across filings

Filing span
38days

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 clocksVermont⏱ VT AG >14 bdayHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 22dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Oct 13, 2022breach begins
Nov 1, 2022discovered · members disagree
notification delay · 52 days
Dec 23, 2022first filing
Jan 30, 2023most 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. DEC 23VT AGVT AG noticefirst filing · no count statedday 0
  2. DEC 30HHS OCRHHS OCR noticestates nationwide total 4,082+7d
  3. DEC 30MA AGMA AG notice3,723 MA residents+7d
  4. DEC 30ME AGME AG noticestates nationwide total 14,337+7d
  5. DEC 30IN AGIN AG noticestates nationwide total 14,337+7d
  6. DEC 30NH AGNH AG notice210 NH residents+7d
  7. JAN 30MT AGMT AG noticemost recent · 7 MT residents+38d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 13, 2022 – Oct 19, 2022
VT AG
Discovered
Nov 1, 2022VT AG + NH AG + MT AGDec 8, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PII
VT AG + HHS OCR + ME AG +3
Attack vector
Unauthorized Access
VT 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)

14,337

Sum of filed state slices

4,079· 28.5% of stated

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

US14,337
MA3,723
NH210
ME134
MT7
IN5

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

38 days

Cadence

~1 / 6.3d

vs. multi-state median

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