Clustered 3 filings across 3 jurisdictions · filed Aug 9, 2024. View entity profile → Other incidents for this victim →
incident inc_5428cab2f1bb40d4 · 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.
CA FL OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 16, 2023 → Sep 22, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 22, 2023
Reported by CALIFORNIA AG filing
Monte Nido experienced unauthorized access to its network between September 16 and September 22, 2023. The incident potentially exposed full names and Social Security numbers of individuals. Monte Nido engaged outside cybersecurity experts, secured systems, and is offering one year of complimentary Experian IdentityWorks credit monitoring to affected individuals.
Monte Nido reported to HHS on 2024-08-09 a ransomware incident affecting 41,662 individuals. Breached information located on Network Server. The incident involved PHI including names, DOB, addresses, SSNs, claims, diagnoses, lab results, and medications. The entity implemented additional administrative, technical, and security safeguards.
Affected (this filing): 41,662
Monte Nido reported a data breach to the Oregon Attorney General. The breach was reported on 2024-08-09. 41,662 individuals were affected.
Affected (this filing): 41,662
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.