← Breach analysis by the Dual Vulnerabilities framework

German Federal Police PATRAS data theft (NN-Crew, 2011)

2011 · Germany · O - Public administration and defence · Data theft via compromised GPS-tracking system server (server takeover, data published)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via compromised GPS-tracking system server (server takeover, data published)

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 19/60

Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) The Bundespolizei and the Zollfahndungsdienst operated PATRAS, their covert GPS target-tracking system, under security requirements that the government response confirms existed for such special-IT systems on the basis of BSI IT-Grundschutz protection standards; every using authority was responsible for its own PATRAS server, and forwarding official e-mail to private accounts was expressly prohibited at BKA, Zoll and Bundespolizei. (2) In operational reality the delivered system was a standalone, internet-discoverable server running the XAMPP web stack with phpMyAdmin - a bundle the response itself calls no security software and not necessary for PATRAS - carrying an existing security gap that an automated vulnerability scan found and exploited on 08-09-2010; the compromise and the data downloads from 25-05-2011 went unnoticed for months and ended only because the attackers announced their publication to a newspaper on 07-07-2011; the attacked systems had never been checked by the BSI or any independent reviewer, and the e-mail-forwarding ban was violated 'weisungswidrig' by an officer over a long period while the Bundespolizei, unlike BKA and Zoll, had not technically blocked automatic forwarding until after the incident. (3) This is a doctrinal-material gap rather than mere weak security: the formal artefacts (Grundschutz-based requirements, the forwarding ban, the standalone architecture as protective design) existed, but none of them translated into the operational configuration, its oversight and its routines - the requirement stayed aspirational while reality was an unpatched, unmonitored, externally reachable server; no source shows leadership deferring, underfunding or overriding a known need, so the break is in execution, and the classification rests on the entry stage (the pre-breach condition that made the system reachable, documented origin and break in the primary government response), with the ten-month detection failure and undetected data downloads sharing the pattern. (4) RM18 (Strategy to Execution lens): the vulnerability-management requirement that existed on paper was not translated into timely patching of the delivered stack - a known-exploitable phpMyAdmin gap stayed open on the production server until an automated scan found it (causal role: Enabling). RM27 (Strategy to Execution lens): configuration baselines and exposure rules were not applied to the deployed systems - the database administration interface was externally reachable and discoverable by scanner, with the unhardened default web stack shipped for convenience (causal role: Enabling). RM34 (Strategy to Execution lens): the monitoring and detection requirements that protect special systems were not implemented or operated - a server holding covert tracking data ran ten months compromised with no detection, and discovery came from the attacker's press notification (causal role: Obscuring). RM11 (Strategy to Execution lens): the specific ban on forwarding official e-mail to private accounts was not translated into enforcement or routines - an officer violated it 'weisungswidrig' over a long period, exposing internal directives and forms, and the technical block existed at BKA and Zoll but was introduced at the Bundespolizei only after the incident (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

Data quality: the row's name field and the task label give 'NN-Crew' as the victim, but the case file's own description reads 'A group calling itself NN-Crew says it has broken into a server used by Germany's Federal Police' and lists initiator_name 'NN-Crew' - NN-Crew is the hacking group's self-designation, so the victim was derived from the description and receiver fields (German Federal Police; the second attacked PATRAS server belonged to the Zollkriminalamt). Source caveats: the row's source_url (h-online.com) no longer resolves (404/422 when opened) and was replaced by the sources actually consulted, above all the German government's answer to a Green party parliamentary question (Bundestag Drucksache 17/6972, 09-09-2011). The response rejects the attackers' claim of having intercepted BKA/Bundespolizei/Zoll network traffic for a year as inaccurate and confirms only the 08-09-2010 compromise and downloads from 25-05-2011; it also denies a direct connection between the officer's private e-mail forwarding and the PATRAS breach, while Der Spiegel's January 2012 follow-up reports the diverted official e-mails as the path into the police network - the entry chain is therefore documented but not fully reconciled between the primary source and the later reporting. The official BSI report on the course of events was classified (VS-NfD) and was never published, so internal details of the security posture rest on the parliamentary record and press accounts. Year 2011 per the row's start_date (08.07.2011); the underlying server compromise began 08-09-2010 per the government response.