Clustered 4 filings across 4 jurisdictions · filing window May 1, 2026 → May 12, 2026. View entity profile → Other incidents for this victim →
incident inc_bc050cf268704666 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Health (basic) · Identity (basic)
IN MA NH OH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 27, 2025
When the intrusion reportedly occurred, per the linked filings
Jan 28, 2026
Reported by NEW HAMPSHIRE AG filing
Ocelot Ventures, LLC (dba Excelas) issued a Massachusetts breach notification regarding a cybersecurity incident affecting customer information. The company offered 24 months of complimentary identity monitoring via Kroll. No identity theft or fraud was confirmed. The specific attack vector and number of affected individuals were not disclosed in this notice.
Ocelot Ventures LLC dba Excelas reported a data breach to the Indiana Attorney General. The breach occurred on 2025-11-27 and was reported on 2026-05-12. 28 Indiana residents were affected. 2,309 individuals affected in total.
Affected (this filing): 2,309
Ocelot Ventures, LLC dba Excelas reported to HHS on 2026-05-12 a Hacking/IT Incident affecting 2275 individuals. Breached information located on Network Server.
Affected (this filing): 2,275
Ocelot Ventures LLC dba Excelas notified the New Hampshire Attorney General of a data event affecting one NH resident. Unauthorized access occurred between Nov 27 and Dec 3, 2025. Excelas discovered suspicious activity on Jan 28, 2026. Affected data includes names, SSNs, health info, and insurance details. Response included law enforcement notification, credit monitoring via Kroll, and regulator notifications.
Affected (this filing): 1
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.