Clustered 2 filings across 2 jurisdictions · filing window Jun 1, 2026 → Jun 5, 2026. View entity profile → Other incidents for this victim →
incident inc_e3f17fe6b2dd4113 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
MA NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 2, 2026 → Apr 3, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 2, 2026
Reported by MASSACHUSETTS AG, NEW HAMPSHIRE AG filings
Manzil Investment Advisors, LLC notified Massachusetts residents of a data breach occurring between April 2-3, 2026. Unauthorized access to computer networks resulted in the potential exposure of personal information, including full names. Manzil engaged external cybersecurity professionals and is offering complimentary identity monitoring services through Kroll to affected individuals.
Manzil Investment Advisors, LLC notified the New Hampshire Attorney General on June 5, 2026, of unauthorized access to its network occurring between April 2 and April 3, 2026. The incident affected approximately two New Hampshire residents, whose names and data elements were potentially accessed. Manzil contained the systems, engaged external cybersecurity professionals, and offered complimentary credit monitoring to affected individuals.
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.