Community Dental
bd_2c0ea5bd71349773 · schema v1 · pii pii-v1
Full breach record for Community Dental →2 incidents on fileThreat-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 mission is to improve the lives of children and adults in our communities by providing needed, accessible, comprehensive, quality oral health care.We have personal data of clients, accounting information, medical data of clients, their medica...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 19, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- HHS OCRbd_8d67a6837dc854b72023-11-17 · +59dVerified
- New Hampshire State AGbd_2b2ad1298b1d2eeb2024-10-22 · +399dVerified by operator
- Massachusetts State AGbd_7fdc21eb5caa3de02024-10-22 · +399dVerified by operator
- Maine State AGbd_eef5da71e0c26cfc2024-10-22 · +399dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Nov 17 (ME), last Oct 22 (ME) — a 340-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.