Clorox Sues Cognizant After $380M Hack

Your Clorox wipes? Out of stock for weeks. Why? Hackers sweet-talked a vendor into handing over network keys. Now Clorox is suing—and it's a wake-up call for every outsourced IT desk.

Clorox Sues Vendor for Coughing Up Passwords in $380M Hack Fiasco — theAIcatchup

Key Takeaways

  • Hackers bypassed MFA via simple phone calls to outsourced service desk—no ID verification.
  • Clorox sues Cognizant for negligence, seeking $380M damages after 'devastating' breach.
  • Outsourcing front-door security invites disaster; expect more lawsuits and in-sourcing.

Imagine this: you’re out of bleach, scrubbing kid vomit off the floor with diluted dish soap. Stores empty. Factories halted. All because some clown at an IT helpdesk — halfway across the world, probably — hit ‘reset password’ for a total stranger on the phone.

That’s the Clorox $380M hack hitting your wallet and shelves. Not some zero-day exploit. Not nation-state hackers. Just a lazy phone call.

Clorox isn’t taking it lying down. They’re suing Cognizant, the vendor running their ‘service desk,’ for gross negligence. And damn, the lawsuit’s language bites.

“Cognizant was not duped by any elaborate ploy or sophisticated hacking techniques,” says the lawsuit, using italics to indicate outrage emphasis. “The cybercriminal just called the Cognizant Service Desk, asked for credentials to access Clorox’s network, and Cognizant handed the credentials right over. Cognizant is on tape handing over the keys to Clorox’s corporate network to the cybercriminal—no authentication questions asked.”

Oof. “On tape.” That’s savage.

How Do You Even Screw Up This Bad?

Hackers dialed up Cognizant’s service desk — outsourced guardians of Clorox’s front door since 2013. Pretended to be an employee. “Hey, forgot my password, MFA reset too?” Boom. Granted. No questions. No callback to a company email. Nada.

Then, slick move: they spotted a juicier IT security account in the network. Called back, impersonated that person. Same script. Same giveaway. Ransomware deployed. Data swiped. $380 million poof.

Cognizant? They claim it was Clorox’s fault. Per the suit, anyway. But Clorox says their contract screamed for basic verification — knowledge-based auth, second calls, the works. Ignored. Employees untrained. “Devastating lie,” Clorox calls it.

Here’s my hot take, absent from the filings: this reeks of 2020’s Twitter hack, where a teen tricked an employee into a phone-based VPN reset. History repeats because companies still treat service desks like Walmart greeters. No badge? No problem.

And Cognizant’s PR? Silent so far. Smart. What do you say? “Oops”?

Your everyday bleach buyer suffered. Plants shut. Shipping snarled. Profits tanked 20% that quarter. Real people — moms, grill dads, cat owners — scrambling for alternatives. While execs point fingers.

Why Outsourcing Your Security Gatekeeper is a Clown Show

Think about it. Clorox, maker of Glad bags and Pine-Sol, hands the keys to network access to Cognizant. A behemoth servicing half the Fortune 500. Should be bulletproof, right?

Wrong. Service desks are the soft underbelly. High volume, low glamour. Reset this, unlock that. Staff turnover? Sky-high. Training? Spotty. Accents on calls? Tricky to spot fakes.

But Cognizant? They’d been at it for a decade. Knew the risks. Still, no logs of verification attempts. No alerts triggered. The suit paints a picture of willful blindness — chasing SLAs over security.

Bold prediction: this lawsuit sparks a vendor purge. Companies will claw back service desks in-house or demand video ID checks. Outsourcers like Cognizant? They’ll bleed clients, or at least hike insurance premiums skyward. Because $380 million stings.

Look, I’ve covered breaches from Equifax to Uber. This one’s dumber. No code vuln. No phishing email. Just social engineering 101 on a vendor who forgot the ‘social’ part means skepticism.

Clorox’s Revenge: Will the Lawsuit Stick?

Clorox wants damages — the full $380M hit, plus more. Breach response, lost sales, reputational goo. Cognizant’s defense? Probably “act of God” or “unforeseeable criminality.” Laughable.

Contracts matter. The suit quotes theirs: verify identity via callbacks, questions only Clorox folks would know. Cognizant skipped it all. “Scant care,” says Clorox. Understatement.

But courts? They love shared blame. Clorox monitored? Had backups? We’ll see discovery docs for the popcorn. Still, precedent: vendors pay big in supply-chain screwups. Think Colonial Pipeline insurers.

Cynical aside — Clorox’s timing? Post-earnings glow-up. Suing the vendor deflects board heat. Smart PR. But hey, if it funds better bleach, I’m in.

Wider ripple: every mid-market firm outsourcing IT help? Audit now. That Indian call center? Might be your weak link. MFA? Great, until the resetter doesn’t check IDs.

The Human Factor That Never Learns

Hacking’s hard, the original story quips. Sometimes. Here? Pathetic. Criminal calls twice, scores god-mode access. Plants ransomware. Exfils data. Clorox crippled for weeks.

Unique angle: this exposes the MFA myth. Okta, Microsoft — reset via phone? You’re one impersonator away from toast. Vendors amplify it. Train ‘em like air traffic controllers, not ticket agents.

Dry humor break: Cognizant’s employees probably got a quota. “Resets per hour.” Security? Bonus round.

Real fix? Zero-trust everything. No standing service desks. AI voice biometrics? Coming. But today? Manual checks, recorded, audited. Or pay the ransom — literal or legal.

Clorox’s saga warns: cheap outsourcing ain’t free. Your network’s front door? Don’t hand it to strangers.


🧬 Related Insights

  • Read more:
  • Read more:

Frequently Asked Questions

What caused the Clorox $380M hack?

Hackers called Cognizant’s service desk, posed as employees, got password and MFA resets without verification. Twice. Ransomware followed.

Why is Clorox suing Cognizant?

Clorox claims Cognizant ignored contract terms for identity checks, handing credentials to criminals on tape. Negligence cost $380M.

Is outsourcing IT service desks safe?

Rarely. High-risk for social engineering. Audit vendors hard or bring it in-house.

Sarah Chen
Written by

AI research editor covering LLMs, benchmarks, and the race between frontier labs. Previously at MIT CSAIL.

Frequently asked questions

What caused the Clorox $380M hack?
Hackers called Cognizant's service desk, posed as employees, got password and MFA resets without verification. Twice. Ransomware followed.
Why is Clorox suing Cognizant?
Clorox claims Cognizant ignored contract terms for identity checks, handing credentials to criminals on tape. Negligence cost $380M.
Is outsourcing IT service desks safe?
Rarely. High-risk for social engineering. Audit vendors hard or bring it in-house.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by Ars Technica Security

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.