Medlink Georgia was listed on 30 June 2026 by the cmdorganization ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). cmdorganization listed 14 organizations that month and 43 in total.
- Listed 142 days ago.
- 708 organizations were listed by all groups in June 2026, see the month.
- 61 in Healthcare that month.
- 199 in US that month.
Updated 2026-11-19 05:41 UTC. Data: public leak-site listings. How we work.
Medlink Georgia
Threat Group Post & Evidence
- Listed by
- CMDOrganization 43 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
We have proudly been serving northeast Georgia since 1976. As a federally qualified health center, we are able to offer uninsured and underinsured patients a sliding fee scale. No one is denied services due to lack of income or insurance status.At MedLink Georgia, we strive to provide comprehensive, coordinated, and continuous care to all our patients. We offer a broad array of primary and preventive care services for patients of all ages, including screening, diagnosis, and management of chronic illnesses.
Kinds of data mentioned
-
Medical or patient records
“…qualified health center, we are able to offer uninsured and underinsured patients a sliding fee scale. No one is denied services due to lack of income or insurance status.At…”
Plain-English summary AI-written
The group says it holds information about a health center’s primary and preventive care services, including screening, diagnosis, and chronic illness management.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Medlink Georgia (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Medlink Georgia directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Medlink Georgia can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching Medlink Georgia A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Medlink Georgia
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
81/100 • CRITICALA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.