Kenny Law Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-22 and was reported on 2025-10-15. 1 Indiana residents were affected. 1,143 individuals affected in total.
Affected (this filing): 1,143
Clustered 2 filings across 2 jurisdictions · filed Oct 15, 2025. View entity profile → Other incidents for this victim →
incident inc_3fd6502d9a2143b8 · merge_method deterministic · confidence 100%
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
Jul 22, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 23, 2025
Reported by NEW HAMPSHIRE AG filing
Kenny Law Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-22 and was reported on 2025-10-15. 1 Indiana residents were affected. 1,143 individuals affected in total.
Affected (this filing): 1,143
Kenny Law Group, LLC notified the New Hampshire Attorney General on October 15, 2025, of a data security incident affecting approximately two residents. Suspicious activity was detected on July 23, 2025, leading to the determination that files containing names, SSNs, driver's licenses, and payment card numbers were accessed without authorization starting July 22, 2025. The firm engaged cybersecurity specialists, offered 12 months of credit monitoring, and implemented additional security safeguards.
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.