LockNet LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-02 and was reported on 2025-11-14. 4 Indiana residents were affected. 449 individuals affected in total.
Affected (this filing): 449
Clustered 2 filings across 2 jurisdictions · filing window Nov 14, 2025 → Dec 5, 2025. View entity profile → Other incidents for this victim →
incident inc_45f758ec3dc242e8 · 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
Aug 2, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 2, 2025
Reported by NEW HAMPSHIRE AG filing
LockNet LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-02 and was reported on 2025-11-14. 4 Indiana residents were affected. 449 individuals affected in total.
Affected (this filing): 449
LockNet, LLC reported an unauthorized access incident to its IT network on August 2, 2025. The breach impacted one New Hampshire resident, exposing names and Social Security numbers. LockNet engaged forensic consultants, provided 12 months of free credit monitoring via TransUnion, and offered fraud assistance. No fraud reports have been received.
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.