---
title: "Harrods attempted cyber intrusion"
description: "What the retained public evidence establishes about the Harrods incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/harrods-attempted-cyber-intrusion-2025"
markdown_url: "https://www.ally.security/incidents/harrods-attempted-cyber-intrusion-2025.md"
stix_url: "https://www.ally.security/incidents/harrods-attempted-cyber-intrusion-2025/stix.json"
---

# Harrods attempted cyber intrusion

Same cluster (attack attempted, contained faster). Limited disruption vs. M&S/Co-op due to faster isolation of systems.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Luxury retail
- **Operational impact:** Limited disruption vs. M&S/Co-op due to faster isolation of systems
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2025, Harrods experienced an incident in its luxury retail environment. The retained source describes the attack path as follows: Same cluster (attack attempted, contained faster). [1](#source-1)

The documented consequence was: Limited disruption vs. M\&S/Co-op due to faster isolation of systems. [1](#source-1)

## Impact

- Documented impact: Limited disruption vs. M\&S/Co-op due to faster isolation of systems. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### May 1, 2025 — Documented public update

The [Harrods is the next UK retailer targeted in a cyberattack](https://www.bleepingcomputer.com/news/security/harrods-the-next-uk-retailer-targeted-in-a-cyberattack/) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Same cluster (attack attempted, contained faster). The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [Harrods is the next UK retailer targeted in a cyberattack](https://www.bleepingcomputer.com/news/security/harrods-the-next-uk-retailer-targeted-in-a-cyberattack/). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/harrods-attempted-cyber-intrusion-2025/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Harrods is the next UK retailer targeted in a cyberattack

news · BleepingComputer

<https://www.bleepingcomputer.com/news/security/harrods-the-next-uk-retailer-targeted-in-a-cyberattack/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 84% confidence · current**  
   Harrods attempted cyber intrusion: Same cluster (attack attempted, contained faster).
2. **Resulted In · 86% confidence · current**  
   Harrods attempted cyber intrusion: Limited disruption vs. M&S/Co-op due to faster isolation of systems.
3. **Affected Organization · 100% confidence · current**  
   Harrods attempted cyber intrusion: Harrods
4. **Occurred At · 100% confidence · current**  
   Documented public update: 2025-05-01
5. **Resulted In · 100% confidence · current**  
   Harrods attempted cyber intrusion: The reviewed source documents the harrods attempted cyber intrusion involving Harrods.

</details>