J Ranck Electric Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-23 and was reported on 2025-03-17. 180 Indiana residents were affected. 5,122 individuals affected in total.
Affected (this filing): 5,122
Clustered 2 filings across 2 jurisdictions · filing window Mar 17, 2025 → May 6, 2025. View entity profile → Other incidents for this victim →
incident inc_8c37af8054fd4f5c · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 23, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 6, 2025
Reported by NEW HAMPSHIRE AG filing
J Ranck Electric Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-23 and was reported on 2025-03-17. 180 Indiana residents were affected. 5,122 individuals affected in total.
Affected (this filing): 5,122
J. Ranck Electric, Inc. reported a data breach affecting 1 New Hampshire resident. Threat actors compromised user credentials on Feb 23, 2025, gaining access to systems containing PII and PHI. The incident was discovered on March 6, 2025, contained by March 10, 2025, and reported to the NH Attorney General on May 7, 2025. The FBI was notified, and affected individuals were offered Experian IdentityWorks.
Affected (this filing): 1
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.