GLOBALClaimed by AnubisFirst sighting
Posted to leak site Nov 26, 2025bd_98bd00f4709944d3
Major customer database leak.
Clustered 3 filings across 3 jurisdictions · filing window Nov 26, 2025 → Dec 23, 2025. View entity profile → Other incidents for this victim →
incident inc_fc911bd4aa594a9b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
NH TX
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 24, 2025 → Nov 3, 2025
When the intrusion reportedly occurred, per the linked filings
Nov 2, 2025
Reported by NEW HAMPSHIRE AG filing
Major customer database leak.
AllerVie Health reported to HHS on 12/23/2025 a Hacking/IT Incident affecting 80521 individuals. Breached information located on Network Server.
Affected (this filing): 80,521
AllerVie Health notified the New Hampshire Attorney General of a data breach affecting 2 NH residents. Unauthorized access occurred between Oct 24 and Nov 3, 2025. Affected data included names, SSNs, and/or driver's license numbers. Notices were mailed Dec 22, 2025, offering credit monitoring. Response included password resets, law enforcement notification, and 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.