Bivash Nayak
24 Jul
24Jul

The case involves cleaning products giant Clorox pursuing legal action against its IT service provider, Cognizant, rather than a former employee directly. Filed on July 22, 2025, in California court, the lawsuit accuses Cognizant's helpdesk of negligence by handing over employee passwords to hackers during a 2023 cyberattack. This enabled attackers to access Clorox's systems, leading to a devastating breach that cost $380 million in damages and disrupted operations for months. The incident highlights the risks of insider threats through third-party vendors, where social engineering (e.g., impersonating staff) exploited weak verification processes. While not a traditional "insider" (no malicious employee intent alleged), it underscores supply chain vulnerabilities in cybersecurity. The story gained widespread attention today (July 24, 2025), as reports detailed embarrassing security lapses, with experts noting it as a cautionary tale for vendor management.Key facts from reports:

  • Incident Background: In August 2023, hackers (believed to be Scattered Spider) breached Clorox via stolen credentials, deploying ransomware-like tools that wiped systems and disrupted supply chains. The attack stemmed from Cognizant's helpdesk resetting passwords without proper verificationβ€”hackers simply called and impersonated employees.
  • Lawsuit Details: Clorox claims gross negligence, citing transcripts where agents gave away passwords despite instructions to verify identities. Damages: $50M in remediation, $330M in lost revenue. Cognizant has not commented publicly.
  • Insider Threat Risks: This case exemplifies "involuntary insiders" via vendors, where poor processes enable external actors. Experts warn of rising third-party risks, with similar incidents (e.g., MGM Resorts hack by the same group) showing the need for zero-trust in helpdesks.
  • Broader Implications: The lawsuit could set precedents for vendor liability in breaches. Clorox's stock dipped slightly on news, but recovery from the 2023 attack is ongoing.
AspectReported DetailsRecommendations
Incident CauseHelpdesk agents reset passwords for imposters without verification.Implement multi-factor verification for support requests; audit vendor processes.
Damages$380M total ($50M remediation, $330M lost revenue); operational disruptions.Conduct regular penetration tests on third-party access; include indemnity clauses in contracts.
Legal ActionSuit filed July 22, 2025; claims gross negligence and breach of contract.Review vendor SLAs for cybersecurity standards; prepare for similar litigation risks.
Threat TypeSocial engineering via vendor helpdesk (insider-enabled external attack).Train staff on phishing/impersonation; use zero-trust for credential resets.
Comments
* The email will not be published on the website.