[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2dij4ogtisijg":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":20,"affectedCountUnit":21,"hasEnglishDescription":4,"severity":22,"dataClasses":23,"description":32,"seoTitle":10,"seoTitleEn":33,"seoDescription":10,"seoDescriptionEn":34,"logoUrl":35,"isVerified":4,"isSensitive":4,"isSpamList":36,"isMalware":36,"company":37},"6a6feb2d3fdf23972ef69756","JeffreyDavidReubenMD2026","Jeffrey David Reuben, M.D. Data Breach","jeffrey-david-reuben-md-2026","","2026-04-18T00:00:00.000Z","2026-08-03T01:13:17.851Z","First-party consumer notice and official state breach records","https:\u002F\u002Foag.my.site.com\u002Fdatasecuritybreachreport\u002Fapex\u002FDataSecurityReportsPage",[14,16,17],"https:\u002F\u002Fwww.mass.gov\u002Fdoc\u002F2026-1232-jeffrey-david-reuben-md\u002Fdownload","https:\u002F\u002Fnebraska.gov\u002Fago\u002Fdata-breach\u002Fdocuments\u002F135ca9b2-a2e4-4fce-856e-b389f1a32050.pdf",17017,"known",null,"people","Medium",[24,25,26,27,28,29,30,31],"Names","Social security numbers","Driver's licenses","Government issued IDs","Financial account information","Payment card information","Medical information","Health insurance information","\u003Cp>\u003Cstrong>The Jeffrey David Reuben, M.D. data breach affected 17,017 people after unauthorized access to the medical practice's network between April 18 and April 19, 2026.\u003C\u002Fstrong> Official notices show that the affected systems contained identity, financial and health information, with the specific fields varying by person.\u003C\u002Fp>\u003Ch2>What happened in the Jeffrey David Reuben data breach?\u003C\u002Fh2>\u003Cp>The practice discovered around April 27, 2026 that an unauthorized actor may have gained access to its network environment. It said it contained the threat, secured the internal environment and began an investigation with external cybersecurity specialists.\u003C\u002Fp>\u003Cp>The forensic investigation and document review concluded on July 15, 2026. The review determined that the affected systems were accessed from April 18 through April 19 and contained personal information belonging to certain individuals.\u003C\u002Fp>\u003Ch2>How many people were affected?\u003C\u002Fh2>\u003Cp>Texas Attorney General record BR-0005211 reports that 17,017 people were affected across the United States. This is the nationwide total reported by the practice.\u003C\u002Fp>\u003Cp>The same record lists 14,172 Texas residents. That figure is a state subset within the 17,017-person total, not a separate population to be added to it.\u003C\u002Fp>\u003Ch2>What information may have been involved?\u003C\u002Fh2>\u003Cp>The official record lists names, Social Security numbers, driver's license numbers, government-issued identifiers such as passports or state IDs, financial account or payment card information, medical information and health insurance information.\u003C\u002Fp>\u003Cp>The information involved varied by individual. A category appearing in the incident record does not mean that every person's file contained all listed fields or that every field was viewed together.\u003C\u002Fp>\u003Ch2>What are the confirmed limits of the incident?\u003C\u002Fh2>\u003Cp>The notice confirms unauthorized network access and that personal information was present in the affected systems. Public documents do not identify the initial access method, technical root cause or responsible actor.\u003C\u002Fp>\u003Cp>The practice said it had no reason, as of the notice date, to believe the information had been or would be misused for identity theft or financial fraud as a direct result of the incident. That statement does not undo the access or guarantee that misuse cannot occur later.\u003C\u002Fp>\u003Ch2>How did the practice respond?\u003C\u002Fh2>\u003Cp>Jeffrey David Reuben, M.D. reported containing the threat, securing its internal systems and using outside specialists to assess the scope. The practice also said it continues to evaluate its security and privacy controls.\u003C\u002Fp>\u003Cp>Written notices were sent to affected individuals, who were offered 24 months of Cyberscout identity-protection services. The personal enrollment code and current deadline appear only in each recipient's official letter.\u003C\u002Fp>\u003Ch2>What should affected people do?\u003C\u002Fh2>\u003Cp>Recipients should first verify the notice through a known contact channel for the practice or the relevant regulator rather than relying on links in an unexpected message. People notified that an identifier or Social Security number was involved can review free credit reports and consider a fraud alert or credit freeze where appropriate.\u003C\u002Fp>\u003Cp>People notified about financial information should review account and card activity, while those notified about medical or insurance information should examine benefit and claim statements for unfamiliar activity. Acting on the fields listed in the recipient's own notice helps keep the response proportionate.\u003C\u002Fp>\u003Cp>If unfamiliar activity appears, the person should contact the relevant bank, healthcare provider or insurer directly and retain the notice and response records. Avoiding unexpected calls or messages that request personal information can also reduce the risk of follow-on scams.\u003C\u002Fp>","Jeffrey David Reuben Data Breach: 17,017 People Affected","The Jeffrey David Reuben, M.D. network breach affected 17,017 people. Review the timeline, information involved and practical protection steps.","\u002Fuploads\u002Flogo\u002Fjeffrey-david-reuben-md-neutral.webp",false,{"name":38,"sector":39,"country":40,"website":10,"websiteArchiveUrl":10,"websiteStatus":41,"websiteCheckedAt":12},"Jeffrey David Reuben, M.D.","Healthcare","United States","No verified public practice website identified"]