← Breach analysis by the Dual Vulnerabilities framework

US Law Enforcement Data Theft and Leak (AntiSec, 2011)

2011 · United States · O - Public administration and defence · Data theft via third-party web hosting provider, mass website defacement and public data leak

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via third-party web hosting provider, mass website defacement and public data leak

Dual vulnerability type

Strategy to Execution

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

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

Why this classification

(1) Strategic expectation: US law enforcement agencies are expected to keep investigative and personal data (officer PII, informant information) classified, minimised and separated from public web content, and to hold suppliers that touch that data to assessed, monitored requirements. (2) In practice: about 70 mostly small-town agencies concentrated their websites and the data stored alongside them with one small Arkansas web-design and hosting firm, Brooks-Jeffrey Marketing; attackers rooted that single server in under a day, kept access for roughly two weeks unnoticed, and copied the entire cache - which Identity Finder's analysis of the published 10GB showed contained 1,923 unique SSNs, 8,214 passwords, birth dates, bank and driver's-license numbers and informant messages held as ordinary email and office files with little separation between sensitive and public data; a security-firm analysis of the dump stated that the SSNs were simply sitting in emails where they had no business being, and recommended a storage policy as the fix. (3) That is a Strategy to Execution gap, not merely weak security: the doctrinal requirements (data classification, retention/minimisation, supplier assurance) existed as a matter of office and sector obligation but were never realised in the operational architecture - one shared, unaudited vendor server for all of it, undetected compromise, and disclosure left entirely to the attacker's leak. The entry technique against Brooks-Jeffrey is undisclosed and not load-bearing; the classification rests on the egress/data-governance stage, the best-documented victim-side gap, with the pre-breach vendor-concentration condition pointing to the same type. RM13 (Strategy to Execution lens): supplier-security requirements, due diligence and monitoring did not translate into controlled third-party operation - the agencies' web presence and its stored data sat with an online-marketing firm that no reporting shows was ever assessed, and its quick root compromise became the breach vector for 70+ agencies (causal role: Enabling). RM16 (Strategy to Execution lens): classification, retention and minimisation requirements were not implemented in systems and processes - SSNs, passwords and informant data lived unclassified in email and office files on public web servers, so far more sensitive data was exposed than any task required (causal role: Amplifying). RM30 (Strategy to Execution lens): isolation requirements were not implemented in architecture and configuration - all tenants' sites and data shared one server with little separation between sensitive and public data, so one root compromise produced a blast radius across 70+ agencies and the simultaneous defacement of all 70+ domains (causal role: Amplifying). A secondary Expertise to Execution pattern sits in the two-week undetected dwell and the relaunched server that carried the attackers' backdoors over - but the second is an unverified attacker claim and cannot be decisive.

Evidence by stage

Risk markers

Sources

Notes

informationisbeautiful row: the case file carries only one sentence and a PCMag URL; all lifecycle evidence comes from own research. The victim is diffuse (70+ agencies, no single organisation); the technically breached system was the shared hosting vendor Brooks-Jeffrey Marketing, which is why the classification rests on the agencies' own data-governance condition rather than on the host's hardening failure. The relaunch-with-backdoor detail (recovery stage) rests solely on AntiSec's own Pastebin statement as reported by CNET - unverified attacker claim, marked speculation and kept off the decisive path. The content analysis of the dump is by Identity Finder, a commercial security firm, not a formal investigation. The attack was retaliation for the arrest of 'Topiary'. CNN's 2011 report could not be opened (extract failed) and is not cited; the LA Times blog and CNET snapshot carry the same facts. incident_id is absent from the case file, left null. Link check: pcmag.com blocks automated access (HTTP 403); the page was opened and read during research.