Confirmed breach. Intrusion Nov 9, 2024–Nov 20, 2024, discovered Nov 19, 2024 — the first regulatory filing landed 72 days later. 6,634 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 >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
6,634
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 9, 2024
When the intrusion reportedly occurred, per the linked filings
InterCon Construction Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-09 and was reported on 2025-01-30. 75 Indiana residents were affected. 6,634 individuals affected in total.
Affected (this filing): 6,634
Leak >30d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
InterCon Construction, Inc. reported a cyber security incident discovered on November 19, 2024, where an unauthorized third party accessed its network. Unauthorized access occurred between November 9 and November 20, 2024. Personal information of two New Hampshire residents was potentially compromised. The company notified federal law enforcement, secured the network, and provided credit monitoring services to affected individuals.
Affected (this filing): 2
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.