HackingHealthcareTechnologyHealthcareVulnerability ExploitData ExfiltratedCustomer Data InvolvedIdentity (basic)Government IDMediumContained

BAESMAN GROUP

bd_6f0ff7c39c7e5084 · schema v1 · pii pii-v1

Severity

Medium

Discovered

May 29, 2023

Filed

Feb 5, 2024

To disclose

36 weeks

Affected

306state residents only

Linked

6 filings

Confidence

65%

Full breach record for BAESMAN GROUP →3 incidents on file

Baesman Group, Inc. notified HealthSun Health Plans members of unauthorized access to a MOVEit Transfer server on May 29, 2023. The attacker exfiltrated PII including names, addresses, DOBs, and member IDs. Baesman Group investigated and enhanced privacy policies. Notices were sent on February 5, 2024.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 36 weeks / 252 days

May 29, 2023

Begins

May 29, 2023

Discovered

Feb 5, 2024

Filed

vs. sector median

+24 wks slower

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

Part of Progress Software Corporation supply-chain incident (2023) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

California State AGbd_dd0e6d5ccd2249d02024-02-12 · +7dVerified
Oregon State AGbd_47adc8a39b47e7952024-02-29 · +24dVerified
California State AGbd_808fe2ae0525500f2024-02-29 · +24dVerified
Washington State AGbd_be036d2299c0c6a22024-02-29 · +24dVerified

Show 1 more filing ↓up to 24d gap

Massachusetts State AGbd_f040b7be18297b812024-02-29 · +24dVerified

Name: BAESMAN GROUP
norm: baesman group

Name: BAESMAN GROUP
norm: baesman group
Industry: HealthcarellmTechnologyllm

Discovered: May 29, 2023
Breach occurred: May 29, 2023
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 5, 2024
Affected individuals: 306state-resident count only
Data types: Identity (basic)Government ID
Data elements: Date of birth
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Moved quickly to take steps recommended by Progress to remedy the issues
Launched an investigation to determine the potential impact of the issues on the security of data
Reviewing and enhancing our existing policies and procedures related to data privacy
Changes made: Reviewing and enhancing our existing policies and procedures related to data privacy
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

Montana State AGFeb 5 · first · this page

California State AG+7d

Oregon State AG+24d

California State AG+24d

Washington State AG+24d

Massachusetts State AG+24d

Pattern: first filing Feb 5 (MT), last Feb 29 (MA) — a 24-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-1077.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 5, 2024
Raw hash: 0f09e2e7d4edb25da9eb97c3bad4d83ef02d6e625ec593df95bbab7dcb2c4902

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityBAESMAN GROUP

Victim entityBAESMAN GROUP

Incidentdiscovered May 29, 2023

Stated responseMoved quickly to take steps recommended by Progress to remedy the issues

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov