Ahold Delhaize confirms cyberattack disrupted store services in Europe and the US

Ahold Delhaize, one of the world's largest food retailers, confirmed that a cyberattack last week disrupted services at stores in Europe and the United States. The source gives no further detail.

An empty row of supermarket checkout lanes with idle registers in a quiet store aisle in the early evening.

Key points

  • Ahold Delhaize is described as one of the world's largest food retail chains.
  • The company confirmed that a cyberattack last week disrupted services at its stores.
  • Both Europe and the United States were affected.
  • The available source text does not describe the attack method, data impact or recovery status.

What was reported

Ahold Delhaize, described as one of the world's largest food retail chains, has confirmed that a cyberattack last week disrupted services at its stores across Europe and the United States.

The text available to us is limited to this confirmation. It does not say how the attackers gained access, which systems were affected, whether any data was taken, or how far services have been restored. We therefore make no assumptions on those points.

Why it matters for Saudi institutions

The case shows that a cyberattack on a retailer can affect services in physical stores across several countries at once. Retail, logistics and consumer-facing organisations in the Kingdom depend on the same kind of connected systems, so the event is a useful prompt to test continuity arrangements rather than a cause for alarm.

Suggested approach

Treat this as a reminder to check readiness. Review how your operations would continue if store, branch or service-point systems were unavailable, and confirm that decision-makers know who leads the response. Follow the company's own statements for confirmed details as they emerge, and avoid relying on unverified reports.

What to do now

  1. Review business continuity plans for the loss of store, branch or point-of-service systems.
  2. Confirm manual or degraded-mode procedures for key customer-facing operations and test them.
  3. Check that incident response roles and escalation paths are current and understood.
  4. Review how critical operational systems are segmented from corporate IT.
  5. Verify that backups of key systems are recent and that restoration has been tested.

How useful was this story?

Need help acting on this?

Our consultants can assess your exposure and map the change to your controls and evidence.

Talk to an expert

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment