Confirmed breach. Intrusion Aug 25, 2024–Aug 26, 2024, discovered Aug 26, 2024 — the first regulatory filing landed 175 days later. 987 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)
987
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 25, 2024
When the intrusion reportedly occurred, per the linked filings
North American Breaker Company LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-25 and was reported on 2025-02-17. 9 Indiana residents were affected. 987 individuals affected in total.
Affected (this filing): 987
Leak >90d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
North American Breaker Company, LLC notified New Hampshire residents of a security incident occurring between August 25-26, 2024. The company detected suspicious activity and malware infection on its network on August 26, 2024. An unauthorized actor accessed systems containing employee, dependent, and business partner data. NABCO contained the incident, investigated, and offered credit monitoring to affected individuals.
Affected (this filing): 20
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.