Confirmed breach. Intrusion May 30, 2023–Jun 2, 2023, discovered Jun 21, 2023 — the first regulatory filing landed 54 days later. 103,775 individuals reported across the linked filings.
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.
Regulatory clocksMaine⏱ ME AG >30d · 54dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
103,775
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME NY
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 30, 2023 → Jun 2, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jun 21, 2023
Reported by MAINE AG filing
54 days
🦞Maine State AGFirst filinglinked via same-victim cross-source · 100%
VNS Health Health Plans reported a data breach that occurred at its HIPAA business associate, Cognizant/TMG. The breach was described as an external system breach (hacking) and resulted in the compromise of names and Social Security Numbers.
Affected (this filing): 1
ME AG >30d · 54d
🗽NEW YORKHHS OCRMost recentlinked via same-victim cross-source · 100%
VNS Health Health Plans reported to HHS on 2023-08-14 a Hacking/IT Incident affecting 103,775 individuals. Breached information located on Network Server. A business associate's software application exposed PHI including names, addresses, SSNs, phone numbers, and emails. The CE notified HHS, individuals, and media.
Affected (this filing): 103,775
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.