Most companies are building walls when they should be building parachutes.

The Summary

  • European grocery chains Ahold Delhaize and Swedish stores hit by cyberattacks — Ahold projecting up to $277M in lost sales, Swedish freezers hit 131°F from system compromise
  • Boards obsess over "can hackers get in" instead of "can we function when they do" — a gap exposed across retail, crypto (Binance's $6.3B breach), and critical infrastructure
  • Ahold restored operations in two weeks; Marks & Spencer still struggling months after their April 2025 breach — resilience architecture matters more than perimeter defense

The Signal

The Swedish freezers melting at 131°F is the perfect metaphor for modern cyber risk. Not because hackers got in — they always get in — but because someone built a system where one breach could turn refrigeration into ovens. The failure wasn't in the firewall. It was in assuming the firewall would hold.

Most companies are still playing defense like it's 2015. They hire former spies to run penetration tests, patch the holes, declare victory. The board gets a slide deck showing red team vs. blue team results. Everyone feels safer. Then an attacker gets through anyway, and the question becomes: can you pull the plug on infected systems without killing the business?

"Sometimes, stopping an attack from spreading means shutting down the very systems that keep you operating."

Ahold Delhaize made a choice: take their websites and apps offline to contain the breach. They chose controlled shutdown over uncontrolled spread. Two weeks later, most services were back. Belgium had online shopping running in one week. That's resilience by design — systems built to fail gracefully and restart cleanly.

Marks & Spencer, by contrast, is still struggling months after their April 2025 breach. Same threat landscape. Different architecture. The delta between those two outcomes is what separates companies that survive from companies that bleed cash while their incident response team argues about blame.

Key differences in cyber resilience:

  • Recovery time: Ahold (2 weeks full restoration) vs. M&S (months of ongoing issues)
  • Containment strategy: Proactive shutdown vs. reactive scrambling
  • Business continuity: Can you fulfill orders, pay staff, and keep facilities running when core systems are dark?

The Binance example is instructive here. A $6.3 billion theft from a crypto exchange that processes billions in daily volume. Binance kept trading. Their hot wallet got drained, but the infrastructure that matches buyers to sellers stayed live. They had built separation between assets and operations. Most companies don't.

The Implication

If you're building for Web4 — agent economies, tokenized assets, autonomous systems — this isn't optional anymore. Your agents need to keep transacting when your main systems are compromised. Your tokenized assets need custody arrangements that survive a breach at the primary platform. The supply chain doesn't stop because you're having a security incident.

Start asking different questions in your next board meeting. Not "can they get in" but "what still works when they do." Test your business continuity like you test your firewalls. Run tabletop exercises where you pull the plug on core systems and see if payroll still runs, if critical orders still ship, if your agents can still execute. The companies that figure this out now will be the ones still operating when everyone else is melting.

Sources

Fast Company Tech