Cyber Incident Victim: Gwinnett Medical Center
Date:
Sep 2018
Location:
United States of America
Summary
Gwinnett Medical Center faced allegations of a data breach and subsequent cover-up, with attackers claiming patient data appeared online and offering contradictory assistance like free credit monitoring. The medical center was investigating the potential incident but provided limited details, leaving the nature and scope unconfirmed. Evidence shared online included images from an internal camera system, though it remained unclear whether the data exposure resulted from a hack or a misconfiguration. Reports indicated conflicting motives from the entity publicizing the claims, complicating verification efforts.
| CIA Posture | Motives | Tactics, Techniques & Procedures |
|---|---|---|
| Available to members | 1 motive | 3 techniques |
| Threat Actor | Type | Location |
|---|---|---|
| 1 actor | Available to members | Available to members |
Description
In late September 2018, Gwinnett Medical Center (GMC) faced public allegations of a potential data breach after attackers claimed to have compromised its systems and accused the organization of concealing the incident. Cybersecurity journalist Steve Ragan of Salted Hash initially reported these claims, noting GMC provided evasive responses to inquiries about the alleged intrusion. The attackers asserted patient data had been exfiltrated and appeared online, though independent verification remained lacking at the time of initial reporting. A Twitter account (@baidu3250617231) subsequently posted supplemental evidence, including photographs purportedly captured from an Axis-brand camera within GMC facilities, though the authenticity and origin of these images were unconfirmed. DataBreaches.net observed that some data circulating online could plausibly belong to patients but emphasized no definitive link to GMC had been established. The threat actors’ motivations appeared contradictory, as they simultaneously accused GMC of negligence while offering free Lifelock identity protection services to alleged victims—a gesture that raised questions about their intent.

The incident’s technical specifics remained unclear, with fundamental details such as attack vectors, data exposure mechanisms (whether through hacking or misconfiguration), and scope of impact unresolved. GMC maintained limited public engagement, declining to provide substantive confirmation or denial of breach claims despite media inquiries. No verified information emerged regarding detection timelines, containment measures, or forensic investigations conducted by the medical center. Potential consequences—including unauthorized access to patient records, financial data exposure, or operational disruption—were neither confirmed nor quantified by independent analysts. The lack of corroborating evidence left critical questions unanswered about the validity of the attackers’ claims, the extent of any data compromise, and the organizational response. Journalistic efforts to obtain additional proof from the threat actors yielded no conclusive findings by the initial report date of September 29.
