Skip to content
cisonews.net

Incident · 8-K Item 8.01

Hanesbrands reports a ransomware attack identified in May 2022

Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.

Hanesbrands Inc. disclosed in a Form 8-K filed under Item 8.01 on May 31, 2022 that it identified a ransomware attack on May 24, 2022. The filing does not state what information was involved or how many people were affected.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at Hanesbrands, and when?

The company says it learned on May 24, 2022 that it had become subject to a ransomware attack. That same sentence of the filing says the company put its incident response and business continuity plans into action to contain the event. The report lists May 24, 2022 as the date of the earliest event reported, and the signature is dated May 31, 2022, seven days later.

How did Hanesbrands respond?

Hanesbrands says its forensic investigation and its assessment of the impact were still under way when it filed. It also reports contact with authorities, and says it is working with them. Outside help is described only by type: legal counsel, a cybersecurity forensic firm, and other incident response professionals. No firm or agency is named.

What did Hanesbrands say about the impact?

The company did not give a view on financial or operational impact. It described itself as early in its work and unable to say whether the event would be material. The filing then ties that uncertainty to its business, operations and financial results. So readers have no figure for lost sales, recovery spending or downtime.

How many people were notified in Washington?

Washington's attorney general lists a report from Hanesbrands Inc. on November 23, 2022, for a breach dated May 24, 2022, with 644 Washingtonians affected. The information it records as compromised is: name, Social Security number, driver's license or Washington ID card number, financial and banking information, full date of birth, passport number, health insurance policy or ID number and medical information. That count covers Washington residents only; the list gives no national total.

What did the Hanesbrands ransomware attack cost?

Hanesbrands put figures on the attack in its annual report for 2022, filed on February 8, 2023.

The ransomware attack hampered its ability to order materials, make and ship orders and process payments in the quarter ended July 2, 2022, and the company estimates it lost about $100 million in sales.

It also booked about $15 million of costs, net of expected insurance recoveries: $14 million mainly from supply chain disruption, in cost of sales, and $1 million mainly for legal, IT and consulting fees.

MeasureAmountPeriod
Estimated lost salesabout $100 millionQuarter ended July 2, 2022
Costs, net of expected insuranceabout $15 million2022
of which supply chain disruption$14 million2022
of which legal, IT and consulting$1 million2022

How many people did Hanesbrands notify in total?

Indiana's attorney general lists Hanesbrands Inc in its 2022 breach report, with notice sent on August 16, 2022 for a breach that occurred on May 24, 2022: 431 Indiana residents and 75,106 people affected in total. The total is the figure the organization reported to Indiana.

What is still unknown?

The filing does not say which systems were affected, whether any data was taken, or whether customers, employees or other individuals were involved. It does not describe a ransom demand, a notification letter, a call-center number or an enrollment deadline. No categories of personal information are listed, so the exposed list is empty. No later filing or amendment on record here adds detail. The state lists above give the only counts: 75,106 people in total by Indiana's record, and 644 Washington residents by Washington's.

How this disclosure's timing compares

Hanesbrands disclosed 7 days after the discovery date its filing gives. Across the 22 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 consumer & retail incidents on cisonews.net

All consumer & retail incidents

Sources

  1. 2026-11-06 · AIndiana Attorney General, 2022 data breach year-to-date report, published November 6, 2026
  2. 2026-11-05 · AWashington State Office of the Attorney General, data breach notifications list, published November 5, 2026
  3. 2022-05-31 · AHanesbrands Inc., Form 8-K (SEC EDGAR), published May 31, 2022
  4. 2023-02-08 · AHanesbrands, Form 10-K for the period ended 2022-12-31 (SEC EDGAR), published February 8, 2023
  5. 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.