Editorial illustration.
Editorial illustration.
Corporate Targets · Cyberattack · 19 of 60

Clorox’s Attack Reached the Factory Floor. The Fight Now Centers on a Help Desk.

A 2026 ruling keeps most of a $380 million vendor lawsuit alive, while financial disclosures show why claimed damages and insured expenses must be kept separate.

The attack that disrupted Clorox’s factories and orders in 2023 has become a dispute over a deceptively ordinary corporate service: helping employees recover access to their accounts. In March 2026, a California judge allowed most of the company’s $380 million lawsuit against service provider Cognizant to continue while dismissing an intentional-misrepresentation claim, according to Law360’s account of the ruling.

That procedural outcome leaves the crucial questions open. It does not establish that Cognizant caused the attack, that Clorox has proved $380 million in recoverable damages, or that the vendor has been ordered to pay. It does put the distinction between an outsourced help desk and a company’s wider security responsibilities at the center of a continuing corporate reckoning.

Clorox’s July 2025 complaint, in its public redacted form, alleges that Cognizant personnel reset credentials without performing required identity checks. The filing reproduces purported call transcripts in which a criminal sought account assistance. Those are the plaintiff’s representations of recorded exchanges, disputed in a case that has yet to establish the vendor’s liability.

According to the complaint, the companies’ relationship had lasted more than a decade, and Clorox had supplied procedures for authenticating requests. Clorox’s theory is that those procedures were not followed at the point where a caller could obtain access. An identity system can be undermined through its recovery process even when the ordinary login screen remains intact. Here, whether that happened as alleged and who was contractually responsible are issues in dispute.

Cognizant offered a sharply different account. In its response reported by The Record, it said it had performed a narrow help-desk role reasonably and did not manage Clorox’s cybersecurity. It blamed shortcomings in Clorox’s own internal defenses and ability to mitigate the attack. The competing positions cannot be resolved by treating the complaint as a completed forensic verdict.

The disruption to Clorox’s business is independently documented in its financial disclosures. Its 2024 financial appendix says the unauthorized activity began on August 11, 2023. The company disclosed the incident publicly on August 14, took systems offline and used manual ordering and processing at reduced operating rates. Order delays and product shortages affected sales and earnings. The systems supporting household brands had become a constraint on getting physical goods to customers.

The same disclosure records about $29 million in incremental fiscal-2024 expenses net of insurance recoveries. It separately identifies $30 million in insurance recoveries during that year. Neither figure is interchangeable with the later lawsuit’s $380 million demand. An expense measure after insurance, a gross recovery and claimed legal damages answer different questions. Adding them together would manufacture a total the accounts do not supply.

In its 2025 financial appendix, Clorox recorded another $70 million in insurance recoveries and said no further recoveries were anticipated. The company described itself as recovered from the attack. That operational assessment can coexist with litigation seeking compensation: restored ordering does not resolve the allocation of historical losses between contracting parties.

Clorox’s 2026 annual filing still identifies the historical attack as materially affecting its strategy, operating results and financial condition. It also discusses risks from identity abuse and trusted third-party relationships. Those are present risk disclosures, not admissions that every alleged failure in the complaint occurred, and not evidence of a new attack.

There is another reason to resist a simple breach-to-bad-results narrative. In its August 2026 earnings release, Clorox attributed much of a quarterly organic-sales decline to comparisons against extra shipments associated with an enterprise-system transition. It had also acquired GOJO. Those developments belong in the current financial picture; they are not automatically damage inflicted by the 2023 intruders.

The lasting vulnerability exposed by the Clorox case is the point where technical access becomes a service request handled by a person. The lasting legal question is who was responsible for defending that point. The attack is documented. The vendor’s liability remains contested.

Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.