Home / News / Article
SecurityWeek · 2 min read

Access Dental Management Data Breach Impacts Over 340,000

Texas-based dental services provider Access Dental Management (ADM) has disclosed a data breach impacting more than 340,000 individuals.

Providing dental care across Texas and in Illinois, Indiana, and New Mexico, ADM says it discovered the incident on May 5 and immediately began an investigation with help from third-party forensic specialists.

The investigation determined that, between May 1 and May 4, hackers had accessed its network and viewed or copied certain data, including personal information.

On October 21, ADM’s review of the compromised information determined that the attacker accessed names, addresses, dates of birth, Social Security numbers, medical information, and health insurance information.

“Upon learning of this incident, ADM moved quickly to investigate and respond to the incident. As part of its ongoing commitment to the security of information, ADM is reviewing and enhancing its existing policies and procedures related to data privacy to reduce the likelihood of a similar future incident,” ADM said in a notice (PDF).

Last week, the organization notified the Texas and Vermont Attorney General’s Offices that 341,049 individuals were affected by the data breach (341,039 in Texas and 10 in Vermont), but the total number could reportedly surpass 455,000.

ADM is sending written notification letters to the potentially affected individuals, encouraging them “to remain vigilant against incidents of identity theft and fraud by reviewing your account statements, explanation of benefits forms, and monitoring your free credit reports for suspicious activity and to detect errors.”

While the organization did not share further details on the cyberattack, the WorldLeaks ransomware group claimed responsibility for the intrusion on June 5.

SecurityWeek has emailed ADM’s parent platform Surge Private Equity for additional information on the incident and will update this article if it responds.

Originally published on SecurityWeek