MalwareHealthcareHealthcareRansomwareRansom DemandedData EncryptedPIIIdentity (basic)PHIHealth (basic)LowContained

Cummins Behavioral Health Systems, Inc.

bd_d278e5a5721ec161 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 9, 2023

Filed

Aug 11, 2023

To disclose

22 weeks

Affected

6state residents only

Linked

5 filings

Confidence

64%

Full breach record for Cummins Behavioral Health Systems, Inc. →2 incidents on file

Cummins Behavioral Health Systems, Inc. notified individuals of a ransomware incident discovered on March 9, 2023. The incident occurred between Feb 2 and March 9, 2023. A ransom note was found, but no files were encrypted. Personal information and PHI may have been accessed. The company engaged a cybersecurity firm and offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 35 days

discovery → filing · 22 weeks / 155 days

Feb 2, 2023

Begins

Mar 9, 2023

Discovered

Aug 11, 2023

Filed

vs. sector median

+10 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_966eb0e320fa7b3f2023-08-11Verified
Indiana State AGbd_ad529a22dc139b622023-08-11Verified
Maine State AGbd_c116fec9cb9a87422023-08-11Candidate
New Hampshire State AGbd_85f75d0b4e2ffc402023-08-18 · +7dVerified

Name: Cummins Behavioral Health Systems, Inc.
norm: cummins behavioral health

Name: Cummins Behavioral Health Systems, Inc.
norm: cummins behavioral health
Industry: Healthcarellm

Discovered: Mar 9, 2023
Breach occurred: Feb 2, 2023 – Mar 9, 2023
Undetected for: 35 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 11, 2023
Affected individuals: 6state-resident count only
Data types: PIIIdentity (basic)PHIHealth (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1078 Valid Accounts
Threat actor: ExternalFinancial
Initial access: valid_credentials

During the incident: Launched an investigation
Engaged a national cybersecurity firm to assist in assessing the scope of the incident
Took steps to mitigate the potential impact to our community
Arranged for you to enroll in a complimentary, credit monitoring and identity theft protection services through IDX
Changes made: Strengthening our systems' security to prevent a similar event from occurring again in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 22 weeks(155 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 ↗

Massachusetts State AGAug 11 · first

Indiana State AGAug 11 · first

Maine State AGAug 11 · first

Montana State AGAug 11 · first · this page

New Hampshire State AG+7d

Pattern: first filing Aug 11 (MA), last Aug 18 (NH) — a 7-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-548.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 11, 2023
Raw hash: eac54bdaa14b699b1368f173d680dc44a0a2bbfedb1e6b8804731ee75e992f47

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityCummins Behavioral Health Systems, Inc.

Victim entityCummins Behavioral Health Systems, Inc.

Incidentdiscovered Mar 9, 2023

Stated responseLaunched an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov