[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fq4izcdlds74n":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":14,"contentUpdatedAt":15,"source":16,"sourceUrl":17,"sourceUrls":18,"pwnCount":26,"affectedCount":26,"affectedCountStatus":27,"affectedCountLowerBound":13,"affectedCountUnit":28,"hasEnglishDescription":4,"contentLocale":29,"availableLocales":30,"translations":32,"severity":35,"dataClasses":36,"description":48,"seoTitle":49,"seoDescription":50,"logoUrl":51,"isVerified":4,"isSensitive":4,"isSpamList":52,"isMalware":52,"company":53},"6a4f7e1ae1bdf4363bce5f47","Aflac Incorporated 2025","Aflac Incorporated 2025 Data Breach","aflac-incorporated-2025","aflac.com","2025-06-12T00:00:00.000Z","2026-07-09T10:55:22.009Z",null,"2025-12-19T00:00:00.000Z","2026-07-19T17:04:25.789Z","Verified U.S. insurance company data breach","https:\u002F\u002Fnewsroom.aflac.com\u002F2025-12-19-Aflac-updates-June-2025-security-incident",[17,19,20,21,22,23,24,25],"https:\u002F\u002Fnewsroom.aflac.com\u002F2025-06-20-Aflac-Incorporated-Discloses-Cybersecurity-Incident","https:\u002F\u002Fwww.sec.gov\u002FArchives\u002Fedgar\u002Fdata\u002F4977\u002F000000497725000128\u002Fafl-20250620.htm","https:\u002F\u002Fwww.aflac.com\u002Fdocs\u002Faflac-cyber-incident-6-24-2025.pdf","https:\u002F\u002Fwww.iowaattorneygeneral.gov\u002Fmedia\u002Fcms\u002F12192025_Aflac_Incorporated_8D84D19EA9D19.pdf","https:\u002F\u002Friag.ri.gov\u002Fmedia\u002F8101\u002Fdownload","https:\u002F\u002Foag.ca.gov\u002Fsystem\u002Ffiles\u002FAflac%20-%20Notice%20Template.pdf","https:\u002F\u002Ftherecord.media\u002F22-million-impacted-aflac-breach",22650000,"known","unknown","en",[29,31],"tr",{"en":33,"tr":34},{"slug":9},{"slug":9},"Critical",[37,38,39,40,41,42,43,44,45,46,47],"Names","Contact information","Dates of birth","Social security numbers","Tax identification numbers","Claims information","Health information","Medical record numbers","Dates of service","Health insurance information","Other personal information","\u003Cp>\u003Cstrong>The Aflac Incorporated 2025 data breach\u003C\u002Fstrong> affected sensitive data associated with approximately 22.65 million people in the U.S. business.\u003C\u002Fp>\u003Ch2>Types of Exposed Data and Risks\u003C\u002Fh2>\u003Cp>The files could contain names, contact details, dates of birth, Social Security or tax IDs, claims and health data, medical record numbers, dates of service, and health insurance information. Not every field was present for every person, so individual exposure depends on the elements listed in each recipient's notice. Identity numbers can support fraudulent credit, account, or tax activity, while health and claims data can enable medical identity theft, false insurance claims, and convincing social-engineering approaches. Because contact information was disclosed only as a broad category, a specific channel such as an email address should not be treated as separately confirmed. \u003Cstrong>Passwords and account credentials were not identified as exposed data.\u003C\u002Fstrong> Password resets were a defensive response and do not establish password theft.\u003C\u002Fp>\u003Ch2>Breach Timeline and Technical Details\u003C\u002Fh2>\u003Cp>Aflac detected suspicious activity on a limited number of systems in its U.S. network on June 12, 2025 and activated its incident-response process. The company said an unauthorized actor obtained personal information that day after using social-engineering tactics to gain access. Access was contained within hours; no ransomware affected the systems, and policy underwriting, claims review, and customer service remained operational. Potentially affected accounts were locked, passwords were reset, and monitoring for suspicious activity was increased. A detailed file review concluded on December 4, 2025 that information requiring legal notification was likely involved, and individual notices began on December 19. No fraudulent use was known when notices were issued, but later misuse remains possible.\u003C\u002Fp>\u003Ch2>User Groups at Risk\u003C\u002Fh2>\u003Cp>The affected population includes customers, beneficiaries, employees, agents, and other people connected with Aflac's U.S. operations. Claims, service dates, and health insurance details can help criminals imitate policy processes when requesting payment, documents, or treatment approval. Employees and agents may face targeted calls, messages, or help-desk impersonation that uses their role and contact details to appear legitimate. People whose Social Security or tax identification numbers were involved have a longer-term credit and tax-identity risk; those with medical record or health insurance identifiers should also watch for unfamiliar treatment, providers, or claims. This record concerns only the 2025 U.S. incident and does not include the aflac.co.jp domain or the separate Aflac Japan incident disclosed in 2026.\u003C\u002Fp>\u003Ch2>Immediate Steps to Take\u003C\u002Fh2>\u003Cp>Anyone who received an Aflac notice or sees a match with this record should verify the notice through the company's known website or official contact channel instead of following a link in an incoming message. Review credit, financial, tax, insurance, and medical records for an unfamiliar application, provider, address, payment, or treatment. If a Social Security or tax identification number was involved, consider a credit freeze and fraud alert, and report suspicious activity promptly to the relevant financial institution, insurer, healthcare provider, and competent authority. \u003Cstrong>Identity and health-data risk cannot be resolved by changing a password alone.\u003C\u002Fstrong> Unique passwords and multifactor authentication are still valuable because stolen personal details can be abused in password-reset and account-recovery workflows. Protection enrollment ended on April 18, 2026; confirm current assistance directly with the company.\u003C\u002Fp>\u003Ch2>Long-Term Security Strategies\u003C\u002Fh2>\u003Cp>Social Security numbers, tax identifiers, medical record numbers, and health histories cannot be replaced as easily as passwords, so monitoring should continue beyond the first few weeks. Check credit files and tax correspondence periodically, and enable alerts for a new provider, changed contact detail, unexplained claim, payment, or service entry in insurance and healthcare accounts. Turn on multifactor authentication wherever it is available and request a second verification channel for sensitive changes made through a call center or agent. Organizations need social-engineering training, restricted privileged access, strong authentication, unusual-session monitoring, and auditable file-access logs. Retain incident and dispute records for later identity or insurance discrepancies. Independently verify urgent requests involving claims, benefits, or medical records.\u003C\u002Fp>\u003Ch2>Check Your Data\u003C\u002Fh2>\u003Cp>A match with this breach record indicates that the searched identifier may be associated with the incident; it does not by itself prove which fields were exposed for that person. Confirm the account's connection with Aflac's U.S. operations and any individual notice, then act on the fields named there. Focusing on the confirmed identity, health, claims, and insurance categories avoids assuming a password leak, while any match involving an identity number still deserves prompt attention. Compare new credit inquiries, tax correspondence, medical bills, insurance claims, and contact-detail changes over time. If a suspicious message refers to the Aflac incident, verify the sender address, telephone number, and urgency through a separate channel; do not provide an identity number, authentication code, or payment detail through an inbound link.\u003C\u002Fp>","Aflac Incorporated 2025 Data Breach (22.7 Million Reported Records)","Aflac Incorporated 2025 Data Breach. 22.7 Million reported records are reported. Reported data: Names, Contact information, Dates of birth. Review the scope…","\u002Fuploads\u002Flogo\u002Faflac-incorporated-2025.png",false,{"name":54,"sector":55,"country":56,"website":10,"websiteArchiveUrl":57,"websiteStatus":57,"websiteCheckedAt":13},"Aflac Incorporated","Insurance","United States",""]