[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6ngaVQN3k1uatK4plXOTaOuoDjVzCoLqVDjtqNVa5Bs":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"company":11,"breachDate":15,"addedDate":16,"modifiedDate":17,"pwnCount":18,"totalRecords":18,"dataClasses":19,"description":27,"source":28,"isVerified":4,"isSpamList":29,"isSensitive":4,"processingStatus":30,"logoUrl":31,"contentUpdatedAt":17,"hasEnglishDescription":4,"severity":32},"6a6774a03c9cd5b93e7daa65","TampaBayDentalImplantsPeriodontics2026","Tampa Bay Dental Implants & Periodontics 2026 Data Breach","tampa-bay-dental-implants-periodontics-2026","tbperio.com",{"name":12,"sector":13,"country":14,"website":10},"Tampa Bay Dental Implants & Periodontics","Healthcare","United States","2026-01-19T00:00:00.000Z","2026-07-27T15:09:20.322Z","2026-07-27T16:11:14.630Z",6400,[20,21,22,23,24,25,26],"Full names","Contact information","Dates of birth","Clinical histories","Treatment notes","Social Security numbers","Financial information","\u003Cp>\u003Cstrong>The Tampa Bay Dental Implants & Periodontics 2026 data breach\u003C\u002Fstrong> involved a ransomware incident affecting a legacy internal server at the Florida dental practice. The practice said it detected the event on January 19, 2026, immediately secured its environment, and conducted a technical assessment. The affected legacy server held a backup of electronic medical records.\u003C\u002Fp>\u003Cp>The U.S. Department of Health and Human Services Office for Civil Rights portal lists 6,400 affected people for Tampa Bay Dental Implants & Periodontics. The federal row classifies the event as a Hacking\u002FIT Incident involving Electronic Medical Record and Network Server locations.\u003C\u002Fp>\u003Ch2>How Was the Tampa Bay Dental Incident Verified?\u003C\u002Fh2>\u003Cp>The primary source is the “Notice of Data Security Incident” on the practice's own tbperio.com domain. The organization directly describes the January 19 detection, ransomware, legacy server and medical-record backup, possible data fields, security improvements, law-enforcement notice, and the 1-866-217-5008 assistance line.\u003C\u002Fp>\u003Cp>The second source is the HHS\u002FOCR federal row reported March 8, 2026 for 6,400 people. The third is ClaimDepot's incident summary, which is consistent with the organization page and HHS record.\u003C\u002Fp>\u003Ch2>Nature of the Event and Timeline\u003C\u002Fh2>\u003Cp>The practice detected a ransomware incident affecting an internal legacy server on January 19, 2026. The incident date is based on the earliest technical activity that can be verified from public sources. This date does not prove that the ransomware entered the system no earlier.\u003C\u002Fp>\u003Cp>The organization says it immediately secured the environment and conducted a technical assessment. Encryption of legacy system logs prevented it from forensically ruling out the possibility of unauthorized access. The HHS March 8 report date is a federal notification date; it was not interpreted as the attack start or completion of a data review.\u003C\u002Fp>\u003Ch2>What Information May Have Been Involved?\u003C\u002Fh2>\u003Cp>According to the official security page, the affected legacy server contained a backup of electronic medical records. Possible fields include names, contact information, dates of birth, clinical history, and treatment notes. For certain people, Social Security numbers or financial information may also have been present in the backup.\u003C\u002Fp>\u003Cp>The practice says it notified all patients out of an abundance of caution, and the combination may vary by person. It should not be assumed that every field belonged to all 6,400 people. Passwords, prescriptions, driver's licenses, bank accounts, and fields not expressly identified as separate categories in the official text were not added.\u003C\u002Fp>\u003Ch2>How Should the Affected-Person Count Be Interpreted?\u003C\u002Fh2>\u003Cp>6,400 is the affected-person count published in the HHS\u002FOCR portal for this Florida dental practice; it is not a number of files, emails, or electronic medical-record rows. The federal portal associates the event with both electronic medical record and network server environments. The affected-person or record count published by the official source represents the reported scope of the incident. It does not mean that every disclosed data category applied to every person.\u003C\u002Fp>\u003Cp>When an official individual notice is available, its listed data categories and protection options should guide the assessment of personal exposure.\u003C\u002Fp>\u003Ch2>Identity, Health, and Financial Risks\u003C\u002Fh2>\u003Cp>Names, dates of birth, contact details, and Social Security numbers for some people can increase targeted phishing or identity-fraud risk. People whose financial information was involved should monitor account activity. Recipients can review credit reports and consider a fraud alert or credit freeze when appropriate.\u003C\u002Fp>\u003Cp>Clinical history and treatment notes create privacy and medical identity-theft risks. Patients should review insurance explanations for services they did not receive or claims they do not recognize. Suspicious healthcare activity should be reported to the provider and insurer, while financial activity should be reported through the relevant institution's known contact channel.\u003C\u002Fp>\u003Ch2>Organization Response and Steps for Individuals\u003C\u002Fh2>\u003Cp>Tampa Bay Dental Implants & Periodontics said it implemented enhanced security logging, strengthened server encryption, and updated access controls after the incident. It notified law enforcement and relevant regulators. The investigation found no evidence of exfiltration or misuse, but unauthorized access could not be fully excluded because the logs were encrypted.\u003C\u002Fp>\u003Cp>Patients who want to learn whether their information may have been involved can call 1-866-217-5008, choose option three, and use the line 24 hours a day. The practice recommends monitoring credit reports and explanation-of-benefits statements. Unverified person counts, data fields, and threat-actor claims are not treated as part of the public incident scope. If a suspicious message or account event appears, it should be verified through the organization’s current official contact channel without using links in the message.\u003C\u002Fp>","Official Tampa Bay Dental security notice, HHS\u002FOCR breach report, and ClaimDepot",false,"completed","\u002Fuploads\u002Flogo\u002Ftbperio_com.png","Low"]