Confirmed breach. Intrusion Oct 5, 2024, discovered Oct 7, 2024 — the first regulatory filing landed 200 days later. 2 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
NH
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 5, 2024
When the intrusion reportedly occurred, per the linked filings
Lion Brothers notified the NH AG of a data event affecting 2 NH residents. Unauthorized access occurred on Oct 5, 2024; detected Oct 7, 2024. Affected data included names, addresses, and government IDs. Response included forensic investigation, credit monitoring, and security policy review.
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.