MalwareHealthcareHealthcareRansomwareData EncryptedTargetedPIIIdentity (basic)LowContained

Robeson Health Care Corporation

bd_a42bc97286b429c6 · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 21, 2023

Filed

Nov 27, 2023

To disclose

40 weeks

Affected

5state residents only

Linked

5 filings

Confidence

65%

Full breach record for Robeson Health Care Corporation →2 incidents on file

Robeson Health Care Corporation notified patients of a malware incident occurring Feb 17-21, 2023. Unauthorized access occurred during this window. The company disconnected its network, engaged forensic specialists, reset passwords, and enabled MFA. Legacy system data containing names and [Extra1] was potentially accessed. No EMR data was accessed. Affected individuals were offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 4 days

discovery → filing · 40 weeks / 279 days

Feb 17, 2023

Begins

Feb 21, 2023

Discovered

Nov 27, 2023

Filed

vs. sector median

+29 wks slower

This filing is one of 5 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_4a1712bc46cd1dbe2023-11-27Verified
Vermont State AGbd_b5def5e6ccd4eeb62023-11-27Verified
Maine State AGbd_ebdd7b926889d25e2023-11-26 · +1dCandidate
New Hampshire State AGbd_5022d51f8ef39a8f2023-12-01 · +4dVerified

Name: Robeson Health Care Corporation
norm: robeson health care
Domain: rhcc1.com

Name: Robeson Health Care Corporation
norm: robeson health care
Domain: rhcc1.com
Industry: Healthcarellm

Discovered: Feb 21, 2023
Breach occurred: Feb 17, 2023 – Feb 21, 2023
Undetected for: 4 daysoccurrence → discovery
Materiality determined: —
Notification sent: Nov 27, 2023
Affected individuals: 5state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1078 Valid Accounts
Threat actor: ExternalFinancial

During the incident: Disconnected our network from the internet
Partnered with computer forensic specialists to restore our systems safely
Reset passwords and enabled multi-factor authentication for all users
Changes made: Enabled multi-factor authentication for all users
Conducted a fulsome and comprehensive review of all legacy system data
Continued to review the policies and procedures in place prior to the event to identify ways to strengthen our security going forward
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 40 weeks(279 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Maine State AGNov 26 · first

Massachusetts State AG+1d

Vermont State AG+1d

Montana State AG+1d · this page

New Hampshire State AG+5d

Pattern: first filing Nov 26 (ME), last Dec 1 (NH) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-890.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 27, 2023
Raw hash: 62b12b35c736653d70f6c1bc3d579ddd08d0c0d533dc9666bd56cec042d4c882

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityRobeson Health Care Corporation

Victim entityRobeson Health Care Corporation

Incidentdiscovered Feb 21, 2023

Stated responseDisconnected our network from the internet

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov