[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2yu0gn9qwiln6":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":17,"affectedCount":17,"affectedCountStatus":18,"affectedCountLowerBound":19,"affectedCountUnit":20,"hasEnglishDescription":4,"severity":21,"dataClasses":22,"description":30,"seoTitle":31,"seoTitleEn":32,"seoDescription":31,"seoDescriptionEn":33,"logoUrl":34,"isVerified":4,"isSensitive":4,"isSpamList":35,"isMalware":35,"company":36},"6a700c918277d58e2e57def0","LuckyLadyCasino2025","Lucky Lady Casino 2025 Data Breach","lucky-lady-casino-2025","luckyladyla.com","2025-05-14T00:00:00.000Z","2026-08-03T03:35:45.736Z","Casino, LLC","https:\u002F\u002Foag.ca.gov\u002Fecrime\u002Fdatabreach\u002Freports\u002Fsb24-624697",[14,16],"https:\u002F\u002Fwww.in.gov\u002Fattorneygeneral\u002Fconsumer-protection-division\u002Fid-theft-prevention\u002Ffiles\u002FDB-Year-to-Date-Report-7_2026.pdf",25851,"known",null,"people","Medium",[23,24,25,26,27,28,29],"Names","Dates of birth","Social security numbers","Driver's licenses","Government issued IDs","Passport numbers","Health insurance information","\u003Cp>The Larry Flynt’s Lucky Lady Casino data breach involved unauthorized access to certain Casino, LLC systems and servers from May 14 through May 18, 2025. Official records state that \u003Cstrong>25,851 people\u003C\u002Fstrong> were affected nationwide, with notifications sent in June 2026.\u003C\u002Fp>\u003Cp>The investigation found that the unauthorized person removed certain information during the access period. The event is therefore a confirmed data breach involving copied personal information, not merely an attempt to enter the network.\u003C\u002Fp>\u003Ch2>How did the incident happen?\u003C\u002Fh2>\u003Cp>After identifying unusual activity on its network, Casino, LLC contained the activity and began an investigation with third-party cybersecurity specialists. The review found that the actor entered certain systems and servers on May 14, remained until May 18 and removed information during that period.\u003C\u002Fp>\u003Cp>A separate data review was conducted to determine whose information appeared in the affected files. The company began notifications on June 10, 2026; the public documents do not identify the initial-access method or the person responsible.\u003C\u002Fp>\u003Ch2>What information may have been involved?\u003C\u002Fh2>\u003Cp>The published scope includes names, dates of birth, Social Security numbers, driver’s license or state identification numbers, passport numbers and health insurance information. The fields varied by person, so the full list should not be assumed to apply to every affected individual.\u003C\u002Fp>\u003Cp>Recipients should rely on the data types listed in their own notice. Passwords and payment card numbers are not included in the published list and should not be added to the incident scope without separate supporting evidence.\u003C\u002Fp>\u003Ch2>Why do these data types matter?\u003C\u002Fh2>\u003Cp>A name combined with a date of birth and Social Security number can make identity theft, fraudulent credit applications and account-opening attempts more convincing. Driver’s license, state ID and passport information may also be used in fraudulent identity-verification processes.\u003C\u002Fp>\u003Cp>Health insurance details can be used in false medical claims or targeted messages pretending to come from an insurer. A message that knows the correct insurer or personal details is not necessarily authentic.\u003C\u002Fp>\u003Ch2>What should affected people do?\u003C\u002Fh2>\u003Cp>Recipients should regularly review credit reports and new credit inquiries, and promptly investigate accounts or applications they do not recognize. A fraud alert or credit freeze may be appropriate depending on the person’s circumstances.\u003C\u002Fp>\u003Cp>Anyone whose health insurance information was involved can review explanation-of-benefits statements and claim histories, then report unfamiliar services to the insurer. Use contact details printed on the insurance card or the organization’s official website.\u003C\u002Fp>\u003Cp>Casino, LLC said it was offering complimentary identity monitoring to affected people. Enrollment should use only the information in the notice sent directly to the recipient or a verified official channel.\u003C\u002Fp>\u003Ch2>Password and communication security\u003C\u002Fh2>\u003Cp>Passwords are not among the data types listed publicly, so this incident does not by itself confirm a password leak. Exposed identity details can still make phishing more persuasive, and multi-factor authentication on email can provide useful additional protection.\u003C\u002Fp>\u003Cp>Do not follow links in unexpected messages claiming to come from the casino, a bank, a credit bureau or an insurer. Never disclose a verification code, account password or full Social Security number during an unsolicited call.\u003C\u002Fp>\u003Ch2>Confirmed scope\u003C\u002Fh2>\u003Cp>The confirmed scope consists of the May 14–18, 2025 access period, the nationwide total of 25,851 people, and recipient-variable identity and health insurance data. The company said it was unaware of attempted or actual misuse at the time of notification; that statement does not guarantee that misuse will never occur.\u003C\u002Fp>","","Lucky Lady Casino 2025 Data Breach (25.9 Thousand People Affected)","The Lucky Lady Casino data breach affected 25,851 people. Review the May 14–18, 2025 timeline, exposed data types and practical safety steps.","\u002Fuploads\u002Flogo\u002Flucky-lady-casino-official.png",false,{"name":37,"sector":38,"country":39,"website":10,"websiteArchiveUrl":31,"websiteStatus":40,"websiteCheckedAt":12},"Larry Flynt's Lucky Lady Casino","Gaming","United States","active"]