On September 25, 2026, Dyfed-Powys Police confirmed it had suffered a cyberattack that was first identified on Monday, September 14, 2026 -- an 11-day gap between detection and public disclosure. Per shattered.io's reporting, the intrusion was flagged internally after the force noticed "unusual activity" on its network that day. The attack disrupted some of the force's non-emergency IT systems -- multiple outlets describe the affected estate as the online public-contact channel, email services, and, per shattered.io, wider "back-office systems" -- all of which were temporarily unavailable and have since been restored. Critically, the force's 999 and 101 emergency call-handling capability remained fully operational throughout, and Dyfed-Powys Police stated it remains fully operational as a force.

The force has found no evidence that personal data belonging to members of the public was accessed or compromised. However, it is still investigating whether information relating to its own staff and employees was accessed or compromised, and has stated it is taking precautionary steps to protect that information and will advise affected colleagues if necessary. The Information Commissioner's Office (ICO) has been notified of the potential personal data breach, consistent with UK GDPR reporting obligations for police data controllers.

The investigation is being led by Tarian, the regional organised crime unit for southern Wales, operating through its cyber-crime unit and supported by external cybersecurity specialists. As of the most recent coverage reviewed (checked through September 27, 2026, across fourteen primary news outlets/trackers -- including The Record, The Register, Cambrian News, Swansea Bay News, BritBrief, Daily Post (x2), GB News, Yahoo News UK, tech-insider.org, Mallory, jointheclaim.com, shattered.io, UKAuthority, and Shropshire Star -- plus independent follow-up analyses), no threat actor or extortion group has claimed responsibility, no ransomware has been confirmed or ruled out, no CVE or specific vulnerability has been disclosed, and the initial access vector has not been made public. jointheclaim.com states explicitly: "Dyfed-Powys Police has not said who carried out the attack, how the attackers gained initial access, whether ransomware was involved, or what data, if any, was actually taken." Dyfed-Powys Police has characterized the response measures taken as "precautionary" while systems are monitored and services are restored.

A note on a sourcing pitfall specifically checked and ruled out during this research pass: automated web-search summarization surfaced a claim that the data-extortion group ExfilSquad "claimed responsibility" for this attack. On verification against primary reporting, this is a conflation with the separate, unrelated Police National Legal Database (PNLD) breach -- ExfilSquad's claimed intrusion there was detected 26 July 2026, three-plus months before Dyfed-Powys Police's 14 September 2026 detection date, and no primary source reviewed (including jointheclaim.com and shattered.io, both of which discuss the incident's unresolved attribution directly) ties ExfilSquad, or any other named actor, to the Dyfed-Powys Police attack. That non-attribution is treated as confirmed fact here, not as an open question.

Because of this evidentiary gap, the MITRE ATT&CK mapping below is deliberately bounded to only the tactics/techniques necessarily implied by the confirmed, disclosed effects -- disruption of named non-emergency IT services (email; online public-contact portal; back-office systems) reached via some undisclosed initial foothold, and a possible, still-unconfirmed compromise of internally held staff records -- rather than a confirmed exploit chain. Discovery techniques are inferred because an intruder would need to enumerate accounts, files/directories, and system context to distinguish and reach these specific non-emergency systems while emergency (999/101) infrastructure stayed unaffected, consistent with network/system segmentation. Collection techniques are inferred from the disclosed scope of the still-open staff-data investigation, including email specifically, since email service was named among the affected systems. A Lateral Movement technique (Remote Services) is likewise inferred as necessarily implied: three distinct internal system categories -- online public-contact portal, email, and wider back-office systems -- were all disrupted while the separately hosted 999/101 emergency call-handling estate stayed unaffected, which requires the intruder to have moved from a single initial foothold across multiple internal hosts/services rather than having gained parallel direct access to each; no specific lateral-movement protocol or tool has been disclosed, so only the base technique is carried, not a sub-technique. Two Impact techniques are listed side-by-side (Service Stop and Endpoint Denial of Service) because the single confirmed technical fact -- named systems went offline for a period and were later restored -- is consistent with either an adversary directly halting/disabling services or a resource-exhaustion/DoS effect, and no source disambiguates which occurred; both are carried as alternative hypotheses for the same observed effect rather than a confirmed technique. No vector, malware family, or actor from any comparable contemporaneous incident (see below) has been linked to this attack by any source reviewed, and none is asserted here. This should be treated as a developing story; attribution, vector, and final data-impact scope may be revised as Tarian's investigation concludes.

This incident sits within a run of UK policing-sector data-protection events cited as sector context by multiple outlets covering the story, none of which has been linked to the Dyfed-Powys Police cyberattack by any source: (1) a September 2023 ransomware attack on ID-card supplier Digital ID that exposed personal data of over 12,500 Greater Manchester Police officers and staff; (2) an August 2026 ICO enforcement notice and reprimand against the Metropolitan Police Service for unrelated data-handling failures (unredacted case documents and a misaddressed email exposing case-related identities); and (3) a July-August 2026 breach of the Police National Legal Database (PNLD) -- the shared legal-reference service used for three decades by all 43 Home Office police forces in England and Wales plus the British Transport Police. The PNLD incident was discovered on July 26, 2026 and publicly confirmed on August 3, 2026: the data-extortion group ExfilSquad claimed responsibility, alleging theft of roughly 1.9GB / ~135,000 records (about 114,000 PNLD subscriber records covering police officers, police staff, criminal-justice professionals and government partners, plus roughly 21,000 email addresses of public "Ask the Police" website users), published on ExfilSquad's dark-web leak site with a sample and a ransom demand; PNLD stated no ransom was paid and found no evidence that passwords or other login credentials were accessed. The PNLD breach was investigated by the National Crime Agency, the North East Regional Organised Crime Unit, and external cybersecurity specialists, with the ICO also notified. Researchers and reporting tied ExfilSquad's access to misconfigured Microsoft Power Pages portals exposing underlying Microsoft Dynamics 365 / Dataverse data (not a Dynamics 365 product vulnerability), and the same group claimed contemporaneous July-August 2026 breaches of the UK Department for Education (600,000+ records claimed), the Ministry of Defence, and the Home Office. No source reviewed connects ExfilSquad, a Power Platform misconfiguration, or any of these other victims to the Dyfed-Powys Police cyberattack; they are documented here strictly as comparative UK public-sector cyber-risk context.