Incident · 8-K Item 8.01
Aflac data breach: about 22.65 million people, from an intrusion contained within hours in June 2025
Compiled from public records. Updated 2026-11-13. By the cisonews.net Desk.
Aflac says personal information on approximately 22.65 million people was involved in the breach it found on June 12, 2025. It gave that count in its annual report for 2025, after finishing its review of the affected files in December 2025. The files held claims information, health information, Social Security numbers and other personal data on customers, beneficiaries, employees, agents and others in Aflac's U.S. business. Aflac says it contained the intrusion within hours and that no ransomware was involved. Texas's attorney general alone lists 2,055,982 Texans. As of its November 2026 quarterly report, Aflac still did not expect a material financial impact.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
How many people were affected by the Aflac data breach?
About 22.65 million, according to Aflac's 2025 Form 10-K. When it first disclosed the breach in June 2025, Aflac said it could not yet give a number. The count came about six months later, when the file review was done.
| Source | Who it counts | Number | Date |
|---|---|---|---|
| Aflac Form 10-K, fiscal 2025 | All individuals whose personal information was involved | about 22.65 million | Filed February 25, 2026 |
| HHS breach portal | People reported to HHS by Aflac as a health plan | 13,924,906 | Submitted August 8, 2025 |
| Texas attorney general | Texans | 2,055,982 | Posted December 22, 2025 |
The federal health breach portal gives a second, smaller figure. It lists Aflac Incorporated as a health plan with 13,924,906 people affected, in a hacking incident on a network server submitted on August 8, 2025. Neither the portal nor the 10-K explains how the 13,924,906 reported to HHS relate to the 10-K's total of about 22.65 million.
Texas's attorney general lists 2,055,982 Texans, posted on December 22, 2025. The Texas record lists names, addresses, Social Security numbers, driver's license and other government ID numbers, medical and health insurance information, and dates of birth among the types involved.
What happened at Aflac?
| Date | Event |
|---|---|
| June 12, 2025 | Aflac identifies unauthorized access to its network; contained within hours, per the company |
| June 20, 2025 | Form 8-K, Item 8.01: no count yet; file review "in its early stages" |
| December 2025 | File review completed; notices to individuals and regulators begin |
| December 22, 2025 | Texas posts its record (2,055,982 Texans) |
| February 25, 2026 | Form 10-K gives the count: about 22.65 million |
| November 5, 2026 | Form 10-Q: no material impact expected; financial impact and insurance coverage still being assessed |
The June 2025 8-K says Aflac started its incident response protocols as soon as it found the access. Its business kept running and its systems were not hit by ransomware. Aflac filed under Item 8.01, not Item 1.05, so it did not treat the incident as material at that point. The guide to Item 8.01 versus Item 1.05 explains the difference.
What information was involved?
The 8-K lists claims information, health information, Social Security numbers and other personal information. It covers customers, beneficiaries, employees, agents and other individuals in Aflac's U.S. business. The 10-K later confirms the data was exfiltrated, not just exposed.
Was the Aflac breach material?
Not by Aflac's own assessment so far. The 10-K for 2025 said Aflac did not consider the incident reasonably likely to have a material impact on its financial condition or results. The November 2026 10-Q repeats that view and adds that Aflac is still assessing the financial impact, including how much insurance will cover. The costs it lists include credit monitoring, identity theft protection and Medical Shield for affected people, plus incident response.
What is Aflac offering affected people?
The 8-K said individuals would be offered free credit monitoring and identity theft protection. The 10-K and the latest 10-Q list the services Aflac is paying for: credit monitoring, identity theft protection and Medical Shield, with a call center for them. The enrollment details are in each person's letter. The guide to credit monitoring offers compares such offers.
How many Washington residents were affected by the Aflac breach?
Washington's attorney general lists a report from Aflac Incorporated dated July 11, 2025, with 432,025 Washingtonians affected; the list leaves the breach date blank. It marks names, Social Security numbers, full dates of birth and health insurance policy or ID numbers. That count covers Washington residents only, within the company's total of about 22.65 million.
What the filings leave open
- How the intruder got in.
- How many of the 22.65 million are customers, and how many are employees, agents or beneficiaries.
- What the incident has cost so far, and how much insurance covers.
How this disclosure's timing compares
Aflac Incorporated disclosed 8 days after the discovery date its filing gives. Across the 21 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 3 days.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other financial services incidents on cisonews.net
- ICW Group Holdings, Inc., Breach notice, first disclosed November 13, 2026
- Point72 Asset Management, L.P., Breach notice, first disclosed November 5, 2026
- The Vanguard Group, Inc., Breach notice, first disclosed November 4, 2026
- Hippo Analytics, Breach notice, first disclosed November 3, 2026; 176,128 affected in total (Indiana Attorney General)
- Baanx US Corp, Breach notice, first disclosed October 30, 2026; 6,594 affected in total (Indiana Attorney General)
Sources
- 2026-11-13 · AU.S. Department of Health and Human Services, Office for Civil Rights, breach portal (cases currently under investigation), published November 13, 2026
- 2025-06-20 · AAflac Incorporated, Form 8-K, Item 8.01 (SEC EDGAR), published June 20, 2025
- 2026-02-25 · AAflac Incorporated, Form 10-K for the fiscal year ended December 31, 2025 (SEC EDGAR), published February 25, 2026
- 2026-11-05 · AAflac Incorporated, Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 5, 2026
- 2026-11-08 · ATexas Attorney General, data security breach reports, published November 8, 2026
- 2026-11-10 · AWashington State Attorney General, data breach notification record, published November 10, 2026
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.