Clustered 3 filings across 3 jurisdictions · filing window Aug 31, 2023 → Sep 7, 2023. View entity profile → Other incidents for this victim →
incident inc_449801da969342e6 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 9, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 9, 2023
Reported by VERMONT AG, MAINE AG filings
Ryders Health Management is now known to everyone, first of all, for its indifferent attitude to the protection of personal data of its clients and employees, as well as corporate information of the company. Absolute indifference of officials is mani...
Ryders Health Management, a skilled nursing and rehabilitation provider, disclosed a ransomware incident detected on July 9, 2023. The attacker encrypted systems and exfiltrated data to demand ransom. Impacted data included names, SSNs, DOBs, medical records, and payment info. Ryders took systems offline, engaged forensic professionals, notified law enforcement, and offered 24 months of Experian IdentityWorks. No evidence of misuse was found at the time of notice.
Ryders Health Management LLC, a healthcare organization, reported a data breach affecting 7,252 individuals. The breach, which occurred on June 29, 2023, and was discovered on July 9, 2023, resulted from an external system breach (hacking). The compromised information included names and Social Security numbers. The company began notifying affected individuals on September 7, 2023, and offered 24 months of complimentary credit monitoring services through Experian.
Affected (this filing): 7,252
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.