Clustered 3 filings across 3 jurisdictions · filing window Nov 5, 2024 → Feb 14, 2025. View entity profile → Other incidents for this victim →
incident inc_e099836aee0547cf · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
PII · Government ID
IN ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 29, 2024
When the intrusion reportedly occurred, per the linked filings
McMillan Electric Company (founded in 1976) is a custom motor and motor products manufacturer for OEMs. MCMILLAN ELECTRIC corporate office is located in 400 Best Rd, Woodville, Wisconsin, 54028, United States and has 226 employees
Jan 13, 2025
Reported by MAINE AG filing
McMillan Electric Company reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-29 and was reported on 2025-02-13. 20 Indiana residents were affected. 6,162 individuals affected in total.
On or about October 29, 2024, McMillan Electric Company (Woodville, WI) discovered on January 13, 2025 that an unauthorized actor had gained access to its network environment and acquired personal information including full names and Social Security numbers. A total of 6,162 individuals were affected nationwide, with 2 Maine residents impacted. Consumer notifications were sent on February 13, 2025. Twelve months of credit monitoring through Identity Defense was offered to affected individuals.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 6,162
Affected (this filing): 2