Confirmed breach. Intrusion Sep 17, 2024, discovered Oct 3, 2024 — the first regulatory filing landed 98 days later (flagged late). 2 individuals reported across the linked filings.
HCF of Warren notified consumers of a data breach affecting patient records. Unauthorized access occurred on September 17, 2024, discovered October 3, 2024. Data exposed included names, SSNs, DOBs, addresses, and medical/insurance info. HCF engaged forensic investigators, notified law enforcement, and offered credit monitoring. No specific victim count disclosed.
VT AG >45 bday
⛰️New Hampshire State AGlinked via multistate filing link · 95%
HCF of Warren Inc. reported that an unauthorized third party accessed its management company's computer systems on September 17, 2024, after suspicious activity was detected on October 3, 2024. The incident affected 2 New Hampshire residents, involving personal information such as names, addresses, and government IDs. The company engaged forensic investigators, notified law enforcement, and offered credit monitoring services.
Affected (this filing): 2
304 days
🦀Maryland State AGMost recentlinked via multistate filing link · 95%
HCF of Warren Inc. (Warren Manor) reported a cybersecurity incident to the Maryland Attorney General on January 10, 2025. An unauthorized third party gained access to the management company's computer systems starting September 17, 2024. The incident affected 2 Maryland residents, exposing names, dates of birth, Social Security numbers, financial account numbers, and medical/insurance information. Warren Manor engaged forensic investigators, notified law enforcement, and offered credit monitoring services.
Affected (this filing):
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.