Confirmed breach. Intrusion Mar 12, 2025–Mar 16, 2025, discovered Mar 17, 2025 — the first regulatory filing landed 126 days later. 892 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 clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
892
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 12, 2025 → Mar 16, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Mar 17, 2025
Reported by NEW HAMPSHIRE AG filing
126 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
King Industries, Inc. notified the New Hampshire Attorney General of a data event affecting 3 NH residents. Unauthorized actors copied files containing names and Social Security Numbers between March 12-16, 2025. Suspicious activity was identified on March 17, 2025. Notifications were sent on July 21, 2025, offering 24 months of credit monitoring.
King Industries Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-03-12 and was reported on 2025-07-21. 1 Indiana residents were affected. 892 individuals affected in total.
Affected (this filing): 892
Leak >90d
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.