DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Bath Fitter Distributing Inc. — December 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Apr 15, 2025 Apr 24, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

3,451

First → last filing

Apr 15, 2025 Apr 24, 2025

Merge confidence

100%

incident inc_ae4d8db49c3a43ac · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe malware. Intrusion Dec 4, 2024–Dec 5, 2024, discovered Dec 5, 2024 — the first regulatory filing landed 131 days later (flagged late). 3,451 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 9-day schedule across 5 filings beginning Apr 15, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
131days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
9days

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 clocksMaine ME AG >90d · 138dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 4, 2024breach begins
Dec 5, 2024discovered
notification delay · 131 days
Apr 15, 2025first filing
Apr 24, 2025most 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. APR 15NH AGNH AG noticefirst filing · 49 NH residentsday 0
  2. APR 18IN AGIN AG noticestates nationwide total 3,451+3d
  3. APR 22ME AGME AG noticestates nationwide total 3,451+7d
  4. APR 23NE AGNE AG noticeno count stated+8d
  5. APR 24MA AGMA AG noticemost recent · 86 MA residents+9d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 4, 2024Dec 5, 2024
NH AG
Discovered
Dec 5, 2024· 1d undetected
NH AG + ME AG + NE AG
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PII
NH AG + ME AG + NE AG +1
Attack vector
Ransomware
NH 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)

3,451

Sum of filed state slices

277· 8.0% of stated

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

US3,451
IN96
MA86
NH49
ME46

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

9 days

Cadence

~1 / 2.3d

vs. multi-state median

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