← Breach analysis by the Dual Vulnerabilities framework

Mossos d'Esquadra agent-data theft (Unattributed hacker, 2024)

2024 · Spain · O - Public administration and defence · Data theft via compromised corporate mailbox, leaked on Telegram

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via compromised corporate mailbox, leaked on Telegram

Dual vulnerability type

Expertise to Execution

Evidence coverage: 5/6 stages, weight 26/60

Decisive stage: containment (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The Mossos d'Esquadra hold precisely the kind of data whose protection is a core operational discipline: prison duty rosters naming officers and commanders with their professional ID numbers and phone numbers. The expectation is doctrinal in the broad sense (data-protection duties, evidenced by the APDCAT notification) and operational in the concrete (hardened endpoints, controlled non-nominal mailboxes, detection of mailbox compromise, full eradication after an incident). (2) In practice, the data sat on an unprotected computer at a penitentiary centre reachable into a shared non-nominal corporate mailbox; the theft beginning by 1 February 2024 went unnoticed and came to light only when the data appeared in a Telegram leak; the body closed the mailbox and CTTI blocked and reset non-nominal mailboxes, yet two days later a second document was published from the same compromised mailbox and a second mailbox was found compromised; the true extent (data of some 500 agents obtained) surfaced only in May 2024 via the union USPAC, beyond the official account of about 70. (3) The decisive stage is containment. The remedies were material and known - close the account, revoke the access, remove persistence, harden the machine - and were decided and applied, so nothing points to a leadership deferral or a missing strategic artefact; the chain broke where the decided remedy was not realised in operations: access persisted and the leak repeated. That is a knowing-doing gap inside the material column, Expertise to Execution. The entry vector beyond the unprotected prison-area computer was never publicly established and is not load-bearing for the reading; the detection gap (external discovery via the leak) points the same way, while the egress (data-governance) and disclosure-incompleteness conditions carry secondary Strategy to Execution and Strategy to Leadership patterns but rest on inference. (4) RM27 (Expertise to Execution lens): the entry path was a computer in the penitentiary area that reporting describes as unprotected, a machine on which specialists had not realised a secure configuration, letting the attacker reach the corporate mailbox (causal role: Enabling). RM38 (Expertise to Execution lens): after discovery the body closed the leaking mailbox and reset credentials, yet a second document leaked from the same compromised mailbox and a second mailbox fell - the attacker's access was not fully scoped or eradicated and persisted and spread (causal role: Amplifying). RM34 (Expertise to Execution lens): monitoring did not raise the mailbox compromise from 1 February onward; the intrusion was discovered externally through the leak and reporting says it caught the body's technical experts off guard (causal role: Obscuring). RM16 (Expertise to Execution lens): duty rosters covering hundreds of agents with professional ID numbers and phone numbers sat in unprotected shared storage that specialists could not inventory or tier - officials could not determine for days what else had been taken - so far more sensitive data was exposed than necessary (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Scale caveat: the dataset row and the February reporting speak of around 70 (then around 140) affected agents; the union USPAC disclosed in May 2024 (via Genbeta) that some 500 agents' data had been obtained and only about 60 published, so the row's figure understates the theft. Attribution: EuRepoC records the actor as not attributed; the Mossos announced on 19-03-2024 the arrest of a person (reported as a minor) as suspected author - the EuRepoC legal_response names the Guardia Civil (17-02-2024) but no primary document tying that measure to this row was found. Entry vector: never publicly established beyond the unprotected prison-area computer giving access to a non-nominal corporate mailbox; the access method was still under investigation at disclosure. The 2016 hack reported as a precedent hit the Mossos union SME, a separate victim, so no recurring-weakness marker is coded for the corps itself. No accessible Mossos or Interior press release for this incident was found; the body's statements are known through press reporting. Per the security policy the Telegram leak itself was not consulted; attacker claims are used only as reported by legitimate press. The response stage was substantially active (risk commission activated, affected agents, APDCAT and the judiciary informed, unions briefed, protective training offered); its coded gap is the incomplete/inaccurate scoping in the official account, resting on inference.