Confirmed breach. Intrusion Nov 17, 2023, discovered Nov 18, 2023 — the first regulatory filing landed 125 days later. 14,503 individuals reported across the linked filings.
Southwest Boston Senior Services, Inc dba Ethos reported a data breach to the Indiana Attorney General. The breach occurred on 2023-11-17 and was reported on 2024-03-22. 1 Indiana residents were affected. 13,418 individuals affected in total.
Affected (this filing): 13,418
🍁Vermont State AGlinked via same-victim cross-source · 100%
Southwest Boston Senior Services dba Ethos notified consumers of a cybersecurity incident discovered on March 13, 2024, involving unusual network activity first detected on November 18, 2023. The incident may have exposed names, addresses, and other personal information. Ethos engaged cybersecurity experts, reported to law enforcement, and provided 24 months of credit monitoring via IDX.
VT AG ≤14 bday
🏛️MASSACHUSETTSHHS OCRlinked via same-victim cross-source · 100%
Ethos dba Southwest Boston Senior Services reported to HHS on 2024-03-22 a Hacking/IT Incident affecting 14,503 individuals. Breached information located on Network Server. The incident involved PHI including names, addresses, SSNs, diagnoses, and health insurance information. The BA implemented additional safeguards and retrained staff.
Affected (this filing): 14,503
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Southwest Boston Senior Services, Inc. (dba Ethos) reported a ransomware incident in November 2023 where its network was encrypted and a monetary demand was made. The incident affected approximately 12 New Hampshire residents, involving PII and potentially SSNs. Ethos contained the breach, restored operations, and notified affected individuals on March 22, 2024, offering credit monitoring services.
Affected (this filing): 12
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.