Skip to content
Breach Index · running record

Coca-Cola fairlife ransomware (July 2026): what the 8-K says

In July 2026 The Coca-Cola Company disclosed that an unauthorized party had reached systems at its fairlife dairy subsidiary, including production systems, and that fairlife’s US production had stopped. This page is the sourced record.

Short answer

Was Coca-Cola hacked?

Yes, at its fairlife subsidiary. Coca-Cola’s Form 8-K of 16 July 2026 says an unauthorized third party accessed part of fairlife’s systems, including production-related systems, and that fairlife’s US production was temporarily suspended; Canadian production was not affected and product quality and safety were not affected.

The Anubis ransomware group later claimed the attack, which Coca-Cola has not confirmed. Coca-Cola had not said whether the incident was material at the time of the filing.

Timeline at a glance

  1. 16 Jul 20268-K: unauthorized access at fairlife; US production suspended. (SEC 8-K)Confirmed
  2. Jul 2026Anubis claims the attack. (Cyber Daily)Unverified claim

Last updated October 31, 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Coca-Cola (fairlife)’s security posture at the time

What Coca-Cola (fairlife) publicly said about its security certifications and controls, how big it is, and how its shares moved, each tied to a source. A certificate covers a stated scope at a point in time; it is not a guarantee about every system. Reviewed 31 October 2026. Compare all 2026 breaches.

Security certifications publicly held

No public certification found.

No public certification found on the company’s own security, trust or compliance pages, in filings, or in the certificate registries searched (BSI, CSA STAR). That is a data point, not proof that none exists.

Size

Revenue $47.9 billion, FY2025 (calendar year). Coca-Cola reports full-year 2025 results (10 Feb 2026)

Listing: NYSE: KO

Share price around the disclosure

-1.1% (Extended trading, 16 Jul 2026). Quartz reported the stock slipped 1.1% in extended trading after the filing. Other outlets reported different moves over different windows, so treat this as indicative only. Quartz, 17 Jul 2026

Coca-Cola (fairlife) incident timeline, in detail

Confirmed = acknowledged by Coca-Cola (fairlife), a regulator filing or a court. Reported = credible reporting Coca-Cola (fairlife) has not fully confirmed. Unverified claim = an attacker or leak-site claim.

16 Jul 2026ConfirmedRansomware / operational technology

Ransomware at fairlife halts US dairy production

What happened. Coca-Cola’s Form 8-K says an unauthorized third party accessed part of the systems of its fairlife dairy subsidiary, including production-related systems, and that fairlife’s US production was temporarily suspended; Canadian production was not affected. The Anubis ransomware group later claimed the attack, which Coca-Cola has not confirmed.

Impact. fairlife’s US production was temporarily suspended, per the 8-K. People or records affected: Not disclosed.

Sources: The Coca-Cola Company Form 8-K, 16 Jul 2026 · Cyber Daily — Anubis claim

The pattern across the record

Certified, and still breached?

We found no SOC 2 or ISO 27001 certification published by Coca-Cola (fairlife). That does not prove it had none; it means none was public.

Operations, not only data

The visible impact was operational disruption. Resilience controls (segmentation, tested restore, the ability to run production while IT is down) decide how long that lasts, and they are only partly covered by a typical SOC 2 or ISO 27001 scope.

What it means for Coca-Cola (fairlife) retailers, distributors and suppliers in the fairlife chain — and what to do

What Coca-Cola (fairlife)’s customers, partners and security teams can do now, based only on what has been disclosed.

  1. 1.Plan for the supplier being down

    If you depend on this company’s products or services, check stock, alternative suppliers and how long you can operate without them.

  2. 2.Ask for restoration status and indicators

    Request the supplier’s restoration timeline and any indicators of compromise you should hunt for in shared connections.

    Open the response checklist
  3. 3.Test your own ransomware readiness

    Use the incident as a tabletop prompt: could you run production with corporate IT offline?

    Open Ransomware Readiness

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed October 31, 2026.

  1. 1.The Coca-Cola Company Form 8-K, 16 Jul 2026 — SEC EDGAR, reviewed 31 Oct 2026
  2. 2.Cyber Daily — Anubis claim — cyberdaily.au, reviewed 31 Oct 2026
  3. 3.Coca-Cola reports full-year 2025 results (10 Feb 2026) — investors.coca-colacompany.com, reviewed 31 Oct 2026
  4. 4.Quartz, 17 Jul 2026 — qz.com, reviewed 31 Oct 2026

Frequently asked questions

Was Coca-Cola hacked?

Yes, at its fairlife subsidiary. Coca-Cola’s Form 8-K of 16 July 2026 says an unauthorized third party accessed part of fairlife’s systems, including production-related systems, and that fairlife’s US production was temporarily suspended; Canadian production was not affected and product quality and safety were not affected.

Did Coca-Cola (fairlife) have SOC 2 or ISO 27001 certification?

We found no SOC 2 or ISO 27001 certification published by Coca-Cola (fairlife). That does not prove it had none; it means none was public.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Coca-Cola (fairlife). Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.

🎉 New here? Use code WELCOME10 for 10% off any plan at checkout