Date
July 2026
Location
United States
Industry
Food & Beverage
Access vector
Unknown
OT targeting
Indirect: IT dependency
Primary peril
None
Impact duration
11 days

fairlife (Coca-Cola) ransomware attack, 2026

DeNexusIncident analysis
Cover image for the incident analysis: fairlife (Coca-Cola) ransomware attack, 2026

The incident path, stage by stage

Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.

Scroll sideways to see every stage.

    IT stagesOT stagesConfirmedPerilReportedImpliedUnknownNot in pathLink not established DeNexus analysis of public sources, as of October 22, 2026
    On this page

      Highlights

        What happened. On July 16, 2026, The Coca-Cola Company said its dairy unit, fairlife, had identified unauthorized access by a third party to a portion of its systems, including its production-related systems, in connection with “a ransomware event”[1]. Production operations at fairlife in the United States were temporarily suspended; Canadian production was not affected[1]. On July 27, the company said the majority of production had resumed at its four US facilities and that the event involved the taking of certain data[2].

        Why it matters. Production stopped at four plants, although no source says that any attacker acted on plant control systems[1][2]. Existing inventory kept retail availability largely unimpacted, and the company expects no material financial impact[2].

        About this analysis. This analysis sets out what is known, stage by stage. The company has disclosed little: no detection date, no stop or restart date, no access route and no cost. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.

        Highlights

        • Coca-Cola disclosed the attack in a statement and an SEC Form 8-K on July 16, filed under Item 8.01, Other Events[1][3].
        • The Anubis ransomware group claimed the attack on its leak site on July 20, claiming 1 TB of data. Neither fairlife nor Coca-Cola has named an attacker[4].
        • On July 27, the company said the majority of production had resumed at its four US facilities, and that retail availability was largely unimpacted thanks to existing inventory[2].
        • Eleven days separate the two statements. Neither gives the dates production stopped or restarted, so that span is not a measured outage[1][2].

        Attack flow

        • Updated: 2026-10-22
        • Intent: Malicious [confirmed]
        • Threat actors: Cyber Criminals [reported | Anubis, own claim]
        • Access vector: Not disclosed [unknown | Company gave no details]
        • IT impact: Malware [confirmed | Ransomware, per the company]; Data Exfiltration [confirmed | Certain data taken]; Data Sabotage [reported | T1486, attacker’s claim]
        • OT targeting: Indirect: IT Dependency [confirmed | Production halt; OT reach not shown]
        • OT sophistication: Not applicable [not in path | No OT technique reported]
        • OT impact: Not in path [not in path | No action on plant control reported]
        • Perils: No Perils [confirmed | Product quality unaffected, per the company]
        • Financial losses: Business Interruption [confirmed]; Cyber Incident Response [confirmed]; Products & Materials [implied]; Assets & Equipment [implied]; Hardware Bricking [implied]

        What happened

        On July 16, 2026, Coca-Cola said in a statement and in an SEC Form 8-K that fairlife had identified “unauthorized access by a third party to a portion of its systems, including its production-related systems”[1][3]. It said fairlife “promptly activated its incident response and business continuity protocols”, was investigating with outside advisors and cybersecurity experts, and had notified law enforcement[1]. The 8-K said the company “has not yet determined whether the incident is reasonably likely to materially affect the Company”[3]. Neither document gives the date the intrusion was detected or the date production stopped.

        On July 20, the Anubis ransomware group listed Coca-Cola and fairlife on its leak site, claiming 1 TB of “confidential data” and to have “locked” servers, and giving the company one week to pay[4][5]. A second Anubis post followed on July 27[5], and SecurityWeek reported a leak-site timer showing publication within two hours unless a ransom was paid[6]. No source located reports that the data was published.

        On July 27, Coca-Cola said fairlife “has resumed the majority of production” at its four US facilities, that retail availability had been “largely unimpacted, due to the availability of existing inventory”, and that “Product quality and safety have not been impacted”[2]. The facilities are in Michigan, Arizona, New Mexico and New York, according to Cheese Reporter; the company has not named the sites[7]. On the second-quarter earnings call the next day, the chief financial officer, John Murphy, said there was “no impact to our second quarter results, nor do we anticipate any material impact to our results in the second half”[8].

        Intent: malicious

        The intrusion was deliberate. The company itself describes unauthorized access by a third party in connection with “a ransomware event”[1], and the attacker’s leak-site post gave the company a week to pay[4]. As far as any source shows, the purpose was extortion. Nothing in the sources suggests the attackers set out to stop milk production for its own sake; the halt is what followed when systems that production relies on were compromised.

        Threat actors: claimed by Anubis

        Anubis claimed the attack on July 20, four days after the company’s first disclosure[4]. Cybersecurity Dive describes Anubis as a group that “emerged in late 2024 as a rebrand of Spinx ransomware”[9]. This is the attacker’s own claim. Neither fairlife nor Coca-Cola has named an attacker in any statement or filing reviewed, so the map shows Cyber Criminals as reported, and the attribution is suspected rather than established.

        Access vector: not disclosed

        Coca-Cola “did not provide any details about how the hackers gained access”, Cybersecurity Dive reported[10]. Researchers have described how Anubis affiliates usually get in: Arctic Wolf’s Stefan Hostetler cited “exploiting internet-facing vulnerabilities”, such as CitrixBleed 2, and “abusing stolen VPN credentials”[9]. That describes the group, not this intrusion, and no source says either method was used against fairlife. The stage is shown as unknown on the map.

        IT impact: ransomware and data taken

        Two things are confirmed by the company: a ransomware event that reached a portion of fairlife’s systems[1], and “the taking of certain data”, of a type it has not disclosed[2][6]. Anubis claims 1 TB[4]. Encryption is reported, not confirmed: the company never says files were encrypted, and the claim that fairlife’s servers were “locked” comes from Anubis[4]. On July 27, the company said it continued “working diligently to restore impacted systems and operations”[2].

        OT targeting: indirect, through IT

        This analysis classifies the incident as an indirect compromise through IT dependency: production stopped because systems that support production were compromised[1]. The company’s phrase “production-related systems” does not say whether production-line control equipment itself was reached, as distinct from IT systems such as scheduling that support production. The halt is confirmed; that plant control equipment was reached is not established, and no source says an attacker acted on process control.

        OT sophistication: not applicable

        No source describes an OT-specific technique, an action on plant control systems or any knowledge of dairy processes used by the attackers[1][2]. The production stop is consistent with ransomware on systems that production depends on, and needs no OT capability to explain it. The stage is marked Not applicable on the map.

        OT impact: none reported

        The company says production was suspended and later resumed, but no source says that a PLC, line controller, filler or instrument was corrupted, reflashed or replaced, and the company said product quality and safety were not affected[2]. In MITRE ATT&CK for ICS terms, the suspension can be read as Loss of Productivity and Revenue. That is an inferred reading of a confirmed business effect, not an action by the attacker on the process, so no OT impact is shown on the map.

        Perils: no physical event

        The company says “Product quality and safety have not been impacted”[2], and no source reports fire, a release, contamination, equipment damage or bricked firmware. Any milk spoiled while production was stopped would be a materials loss from the halt, not a peril.

        Four dairy plants stopped without any source reporting an attack on a single plant controller.

        Financial losses: no figure disclosed

        No figure has been disclosed for any consequence. The company says the incident “has not had, and is not reasonably likely to have, a material impact” on its financial condition or results[2]. For scale, CBS News reported that, according to Coca-Cola, fairlife’s annual sales top $3 billion[11]; no source ties that figure to a loss.

        Loss evidence

        • Confirmed: Lost revenue and productivity (US production suspended, no amount disclosed); Network event response and recovery
        • Implied: Materials and product loss; Startup and return-to-service validation; Ransom extortion (demand known only from the attacker); Server replacement; Computer and laptop replacement
        • Not supported: Contract violation or obligation; Customer retention; Market valuation; Sensitive personal data event response; Network device replacement; Embedded device replacement; Industry regulation liability

        The chief executive, Henrique Braun, said on the earnings call that “we did not have any impact on the supply on the consumer service during that period”[8]. No ransom demand amount or payment has been reported.

        What this incident shows

        fairlife follows a familiar pattern: ransomware on systems that support production, and a halt at every plant that depends on them[1]. What limited the damage was the stock rather than the plants: retail availability was largely unimpacted because of existing inventory, and the company reported no impact on supply to customers[2][8].

        The disclosure leaves the key questions open. The company has not said how the attackers got in, when production stopped or restarted, what data was taken, or whether plant control equipment was reached[1][2][10]. For anyone assessing this kind of risk, the eleven days between two statements are a span, not a measured outage, and the absence of a figure is not evidence of a small loss.

        References

        1. The Coca-Cola Company. “The Coca-Cola Company Announces Technology Disruption Involving fairlife Operations.” Press release, 16 July 2026. investors.coca-colacompany.com/news-events/press-releases/detail/1166/the-coca-cola-company-announces-technology-disruption-involving-fairlife-operations
        2. The Coca-Cola Company. “The Coca-Cola Company Announces Significant Progress in Restoring fairlife Operations Following Technology Disruption.” Press release, 27 July 2026. investors.coca-colacompany.com/news-events/press-releases/detail/1167/the-coca-cola-company-announces-significant-progress-in-restoring-fairlife-operations-following-technology-disruption
        3. The Coca-Cola Company. “Form 8-K, Item 8.01 (Other Events).” SEC EDGAR, filed 16 July 2026. sec.gov/Archives/edgar/data/0000021344/000162828026048466/ko-20260716.htm
        4. Kovacs, Eduard. “Ransomware Group Threatening to Leak Data Stolen From Coca-Cola’s Fairlife.” SecurityWeek, 22 July 2026. securityweek.com/ransomware-group-threatening-to-leak-data-stolen-from-coca-colas-fairlife/
        5. “Anubis.” RansomLook, ransomware group tracker, read 22 Oct. 2026. ransomlook.io/group/anubis
        6. Kovacs, Eduard. “Coca-Cola Confirms Data Breach After Fairlife Ransomware Attack.” SecurityWeek, 27 July 2026. securityweek.com/coca-cola-confirms-data-breach-after-fairlife-ransomware-attack/
        7. “Fairlife Has Resumed Majority Of Production At Its Four US Facilities.” Cheese Reporter, 31 July 2026. cheesereporter.com/news/production-supply-chain/2026/07/31/fairlife-has-resumed-majority-of-production-at-its-four-us-facilities/
        8. The Coca-Cola Company. “Corrected Transcript: The Coca-Cola Co. (KO-US), Q2 2026 Earnings Call, 28-July-2026 8:30 AM ET.” Coca-Cola Investor Relations, 28 July 2026. investors.coca-colacompany.com/_assets/_02e697116701934d72c9696476a1da96/cocacolacompany/db/880/11126/webcast_transcript/CORRECTED+TRANSCRIPT++The+Coca-Cola+Co.%28KO-US%29%2C+Q2+2026+Earnings+Call%2C+28-July-2026+8+30+AM+ET.pdf
        9. Jones, David. “Threat group claims credit for ransomware attack on Coca-Cola’s dairy unit.” Cybersecurity Dive, 22 July 2026. cybersecuritydive.com/news/threat-group-ransomware-coca-colas-dairy-Fairlife/825900/
        10. Jones, David. “Coca-Cola restores most production capacity at dairy unit after ransomware.” Cybersecurity Dive, 27 July 2026. cybersecuritydive.com/news/coca-cola-restores-most-production-capacity-at-dairy-unit-after-ransomware/826250/
        11. Cerullo, Megan. “Coca-Cola Halts U.S. Fairlife Milk Production after Cyberattack Hits Systems, Company Says.” CBS News, 17 July 2026. cbsnews.com/news/coca-cola-fairlife-milk-cyberattack/