Call 4 Health, Inc.
bd_a2cbcb3bb388410a · schema v1 · pii pii-v1
Full breach record for Call 4 Health, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
Our medical answering service solution was the first program offered by Call 4 Health. With over 20 years of experience, we understand the importance of a well-designed answering service solution and can customize it to match your needs.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 6, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitelockbit_3bd_1e1dc4857761cbf82024-04-19 · +17dVerified by operator
Regulatory filings (3) · sorted by filing gap
- HHS OCRbd_570ba8268591e39c2024-05-17 · +11dVerified
- Maine State AGbd_bbaefcb7a54b28b22024-07-08 · +63dVerified by operator
- Massachusetts State AGbd_d2ea833bf882f4162024-07-12 · +67dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing May 6, last Jul 12 (MA) — a 67-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.