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

Wheels Manufacturing, LLC — October 2024 breach

Clustered 5 filings across 5 jurisdictions · filed Dec 6, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

683

First → last filing

Dec 6, 2024

Merge confidence

100%

incident inc_30336a014ecd434b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Oct 7, 2024–Nov 4, 2024, discovered Nov 4, 2024 — the first regulatory filing landed 32 days later. 683 individuals reported across the linked filings. Data reported: PII, Financial account, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
32days

Discovered → first regulatory filing

Discovery variance
8days

Range of discovered_at dates across filings

Filing span
0days

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 bdayMaine✓ ME AG ≤30d · 24dFull clock table in Litigation Timeline

Incident timeline

Oct 7, 2024breach begins
Nov 4, 2024discovered · members disagree
notification delay · 32 days
Dec 6, 2024first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. DEC 6NH AGNH AG noticefirst filing · 8 NH residentsday 0
  2. DEC 6ME AGME AG noticestates nationwide total 683day 0
  3. DEC 6IN AGIN AG noticestates nationwide total 683day 0
  4. DEC 6VT AGVT AG noticeno count statedday 0
  5. DEC 6MA AGMA AG noticemost recent · 19 MA residentsday 0
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 7, 2024 – Nov 4, 2024
NH AG
Discovered
Nov 4, 2024VT AGNov 12, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · PCI · PII
NH AG + ME AG + VT AG +1
Attack vector
Misconfiguration
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)

683

Sum of filed state slices

39· 5.7% of stated

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

US683
MA19
NH8
IN7
ME5

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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