Skip to content
TRANSMISSION ACTIVE
// FREQ: TECH SECTOR EPISODE: 035 STATUS: SECURE

035 Coca-Cola’s Fairlife Ransomware, Nike’s 1.4TB Leak, and the Rise of Extortion Without Encryption

JUMP POINTS //
01:03

Ransomware That Stopped the Bottling Line

July 16, 2026. Unauthorized access reached fairlife’s production systems and US operations were suspended. Our CISO on why manufacturing control systems are a different kind of target than a records database.

04:12

The Pay-or-Don't-Pay Decision

Coca-Cola did not negotiate. The math behind that call — what the stoppage costs per day, what the demand is, and whether you are confident you can restore without being hit again.

05:37

Why Canada Kept Running

US production stopped and Canadian operations were untouched, which points to network isolation doing exactly what it is supposed to do.

06:42

Nike's 1.4 Terabytes

January 26, 2026. WorldLeaks published product designs, manufacturing workflows, pricing, audit results, supplier information — and no encryption anywhere.

07:31

What Did They Steal Then?

Nike said no customer or employee personal data was in the leaked set. Our CISO’s reaction to that statement is the most candid moment in the episode.

09:21

Nothing to Restore

Your backup strategy is irrelevant when nothing was locked. Why exfiltration-only extortion defeats every recovery plan built in the last decade.

12:23

241 Days Inside the Network

Moving terabytes out is not a smash and grab. It is months of quiet work — and the suspected entry was a third-party partner in the supply chain.

17:14

If You Don't Define Materiality, Someone Else Will

The sharpest advice in the episode. Define your disclosure threshold now, document the reasoning, and be able to defend it — because the regulator and the opposing attorney will define it for you otherwise.

// INCOMING SITREP

The episode covers what happened. The SITREP is the exercise — how to tabletop the breach where every system still works and the data is simply gone.

ACCESS THE BRIEF »

TRANSMISSION LOG //

Two of the biggest cyber events of 2026, and they failed in completely opposite directions.

One stopped physical production at four plants. The other took 1.4 terabytes out of a global brand and never encrypted a single file. Neither looks much like the breach most executives picture when they think about cyber risk — and that is the point of this episode.

Coca-Cola’s Fairlife Ransomware

On July 16, 2026, The Coca-Cola Company announced that fairlife, LLC, its dairy subsidiary, had identified unauthorized third-party access to a portion of its systems — including its production-related systems — in connection with a ransomware event.

This was not a records breach. It stopped manufacturing.

Our CISO spent time on why that distinction matters, and it comes down to what a modern plant actually is. Bottling lines are run by control systems. The bottles drop, the milk pours, the cap seals — and people monitor machines rather than performing the steps. Compromise the control systems and you have not stolen anything. You have switched off a factory.

US production operations were temporarily suspended. Canadian operations were not impacted. Product quality and safety were not impacted.

The Group and the Decision

The Anubis ransomware group listed Coca-Cola and fairlife on its leak site on July 20, claiming 1 TB of stolen data, and told BleepingComputer it had encrypted the company’s Nutanix systems.

Coca-Cola did not negotiate. On July 27, 2026, the company confirmed data was taken and said the majority of production had resumed across its four US facilities — eleven days from identification.

Our CISO walked the decision behind that, because it is the one most organizations have never modeled:

“Once production stopped, how much money did that cost? And then how much did they want? Based on that, you have to make a decision. The executive has to make a decision. Do we pay? Do we not pay?”

The second half of that calculation is the part teams forget — not just whether you can restore, but whether you are confident the attacker cannot simply come back in. Her read is that Coca-Cola’s confidence came from preparation: they had almost certainly rehearsed this.

The Detail Worth Copying

One observation from the episode that should go straight into your architecture review.

US production went down. Canadian production kept running. That strongly suggests network isolation between the two environments — and if those networks had been flat, the same intrusion would have taken every plant offline simultaneously.

Segmentation is not an abstract control. In this incident it was the difference between a regional outage and a continental one.

For context Actual added: the Verizon 2026 Data Breach Investigations Report found ransomware present in 48% of breaches, and that 69% of ransomware victims did not pay. Coca-Cola’s shares fell roughly 4% the day after disclosure.

Nike’s 1.4 Terabytes

The opposite failure mode entirely.

On January 26, 2026, a group called WorldLeaks published approximately 1.4 terabytes of Nike’s internal material. No encryption. No production stoppage. And according to Nike, no customer or employee personal data in the leaked dataset.

The material reportedly included product designs, manufacturing workflows, pricing, audit results, partner data, production plans, supplier information, and internal training materials.

“What Did They Steal Then?”

Our CISO did not accept the framing, and said so plainly:

“Nike investigated and said no employee or customer data was found. What did they steal then? You’re telling me a group got in and left with what — public documents off the company’s external website? That’s a little suspicious, I would say.”

Her assessment was that the statement reads like something drafted by attorneys. Technically accurate, possibly complete, and unlikely to be reassuring to anyone paying attention.

That is a lesson independent of whether Nike’s statement was right. A disclosure that is precisely worded and lands as evasive costs credibility without buying anything — and your customers are reading it the same way our CISO did.

Nothing to Restore

WorldLeaks operates on exfiltration and extortion rather than encryption. Nothing gets locked, so there is nothing to bring back.

“They got in. They didn’t encrypt, so they’re not doing ransomware. They did reconnaissance, found what they thought was worthwhile, and took it. It’s like somebody came into your house, walked around looking for valuables, and just took them. They didn’t break anything.”

Which means your backup strategy — the thing every disaster recovery plan is built around — is irrelevant to this attack. And as she asked directly: does anyone actually test for this case?

Why Steal Designs?

Actual made the commercial case concrete with a conversation he had with his teenage son, who buys knockoff Jordans without hesitation because, in his words, nobody can tell. His generation does not carry the stigma an older one did.

That is a market. Supplier lists, production workflows, and unreleased designs are precisely what a counterfeiter needs to close the quality gap — and a limited-edition release loses its scarcity premium the moment the knockoff is indistinguishable.

No breach notification statute covers any of that. No regulator is waiting. The injury is purely commercial and it unfolds over years.

The Supply Chain and the Dwell Time

The suspected entry point was a third-party partner system in the supply chain — though this has not been confirmed. Our CISO’s framing: Nike can secure Nike. Can the small supplier Nike depends on secure itself to the same standard? That gap is the way in.

And on how long they were there: IBM puts the average time to identify and contain a breach at 241 days. Moving 1.4 terabytes is not a smash and grab. It is the better part of a year of quiet work.

The Three Marching Orders

1. Name Your Crown Jewels — and Check What You Are Actually Securing

Our CISO’s observation is the thesis of the episode. Most organizations scope their critical assets to whatever a regulator or auditor would ask about: personal information, financials, credentials. That scoping is rational and it is frequently wrong.

Fairlife’s critical asset was not PII. It was uptime. For a technology company it is more likely source code, unreleased roadmap, pricing models, or customer lists — none of which carry a regulatory designation and all of which would hurt badly to lose.

Align the security program to the business, not to the auditor’s checklist.

2. Test the Scenario Where Nothing Gets Encrypted

Everyone drills ransomware recovery. Almost nobody drills the other one.

“Make sure you’re testing — what if they don’t encrypt and they just take all your critical data? Your data is out there. What now?”

That exercise is mostly reputational and legal rather than technical, which is exactly why the usual participants cannot run it.

This is where the episode hands off. We cover what happened here; the companion SITREP is the exercise. Extortion Without Encryption: The Tabletop Your Ransomware Plan Is Missing gives you the scenario, the six injects in sequence, who has to be in the room, and the five questions that turn out to have no owner in most companies.

3. Define Materiality Before You Need It

The sharpest thing said in this episode, and it applies to any company that is public, heading there, or signing enterprise contracts with disclosure obligations:

“If you don’t define materiality, the regulator will. The other attorney will. And if it doesn’t match what you believe materiality is, you’re going to be fined a lot more.”

The defensible position is a documented one — we did the research, we consulted industry and agency guidance, we set the threshold here, and this incident did not reach it. Coca-Cola filed its Form 8-K under Item 8.01 and stated it had not yet determined material impact. That is a judgment made in days against a framework that existed beforehand.

Write the decision tree now. Name who makes the call. You cannot draft it while a countdown is running.

Execute the Standard

Two incidents, two completely different losses. Coca-Cola lost production. Nike lost designs and supplier lists and, by its own account, not one customer record.

The connective thread is that in both cases, what got taken was not what the security program was pointed at. These are not small companies without budget — they are organizations with real security functions that got hit outside the expected blast radius.

So the question is not whether your controls are good. It is whether they are aimed at the thing that would actually hurt you to lose.

If you need help running the exercise, building the crown jewel analysis behind it, or producing the evidence an enterprise buyer will ask for, that is the work we do. Verify your security posture or book a strategy call.

Next week we get into the Match Group breach.

Mission success starts with knowing what is actually critical.

Execute the standard.

// DECODED TRANSCRIPT

Access the full text logs of this transmission for compliance and review purposes.

SILENCE THE NOISE. AMPLIFY THE SIGNAL.

INTELLIGENCE IS USELESS IF YOU AREN'T LISTENING.

Join The Watch to receive New Episode Alerts, Strategic Breakdowns, and Guest Intel delivered to your inbox.