Confirmed breach. Intrusion Jan 24, 2025–Jan 25, 2025, discovered Jan 25, 2025 — the first regulatory filing landed 80 days later. 1,466 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine⏱ ME AG >30d · 80dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
1,466
Data types
1
PII
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 24, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jan 25, 2025
Reported by MAINE AG filing
80 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
KWS Manufacturing Company LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-24 and was reported on 2025-04-15. 1 Indiana residents were affected. 1,466 individuals affected in total.
KWS Manufacturing Company, LLC (Burleson, TX) reported a hacking incident in which an unauthorized third party accessed its computer systems during January 24–25, 2025, obtaining company files containing personal information. The breach was discovered January 25, 2025. 1 Maine resident was affected out of 1,466 total. Affected individuals were offered 12 months of Equifax Credit Watch Gold monitoring. Law enforcement was notified.
Affected (this filing): 1
ME AG >30d · 80d
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.