Clustered 2 filings across 2 jurisdictions · filing window Jun 30, 2023 → Jul 5, 2023. View entity profile → Other incidents for this victim →
incident inc_e5351595e3f44cea · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Government ID
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.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 31, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 5, 2023
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Realm IDX Inc. experienced a data breach impacting 3 Maine residents, which was attributed to an external systems breach at a third-party vendor. The incident was discovered on June 5, 2023, with the breach having occurred on May 31, 2023. The compromised data included Social Security numbers. Affected individuals were notified on June 30, 2023.
Affected (this filing): 3
REALM IDx, Inc. and Ambry Genetics reported a third-party vendor breach involving Vitality. Vitality, a provider of employee wellness benefits, was impacted by a zero-day vulnerability in Progress Software's MOVEit Transfer application. The incident resulted in the exposure of names and Social Security numbers for 2 New Hampshire residents (former and current employees). Notification letters were mailed on June 30, 2023, offering credit monitoring services.
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.