← Breach analysis by the Dual Vulnerabilities framework

El Salvador PNC data theft & doxing (FocaLeaks, 2021)

2021 · El Salvador · O - Public administration and defence · Data theft and publication (hacktivist intrusion, doxing)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft and publication (hacktivist intrusion, doxing)

Dual vulnerability type

Strategy to Leadership

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

Decisive stage: response (tie-break: post-breach stage) · Alternative: Expertise to Execution

Why this classification

(1) The PNC holds crown-jewel data: personnel identities of ~30,000 agents, and - via the Imperium platform - civil records on Salvadoran citizens and criminal investigations; the strategic expectation for such an institution is an authentication model proportionate to that data, plus honest, timely communication to its own personnel and the public when such data is compromised. (2) In early September 2021 the hacktivist collective FocaLeaks exfiltrated and published the agents' records (DataBreaches.net counted ~37,000 active agents, including Imperium logins, IMEI numbers and PINs). The intrusion mechanism - a police mobile app whose API requests carried no tokens and whose dumped IMEI+PIN logins kept working after the leak - is the attackers' own, unverified claim that PNC never confirmed, so it is recorded but not treated as load-bearing. PNC did not disclose publicly for about three weeks: it took the website offline, deactivated officer applications and placed Imperium under UTIT control on 3 September, while the leak spread; on 21 September the director confirmed investigations yet framed the leak as an old database, even though agents recognised their own current data in the dump and filed criminal complaints fearing for their lives, and no protective notification to the affected officers is documented. (3) The decisive gap sits in the response/disclosure stage: the expectation that leadership communicate accurately about a live incident is doctrinal (strategic-level; the director's own statement is the artefact), and the chain broke at leadership - a leak-triggered, delayed disclosure and a minimising public framing contradicted by the institution's own emergency actions, the classic Strategy to Leadership pattern of public account diverging from the documented situation. The entry/detection/egress gaps point to Expertise to Execution (known authentication, monitoring and egress controls not realised), but the entry mechanism rests on attacker claims (speculation, which cannot win a tie-break) and the response stage is furthest from the breach moment and best documented by the victim's own words - it wins the tie-break; the E2E-dominant share marks the row borderline. (4) RM39 (Strategy to Leadership lens): leadership's disclosure behaviour diverged from what the incident demanded - silence for ~3 weeks, disclosure only forced by the attackers' publication, then a director's 'old database' framing contradicted by PNC's own Imperium takeover and officers finding current records (causal role: Constraining). RM43 (Strategy to Leadership lens): leadership did not treat the 30,000+ exposed agents as affected parties owed care - they discovered their own exposure in the leak and filed complaints about danger to their lives, with no documented notification, credential rotation programme or protection offer (causal role: Amplifying). RM16 (Strategy to Leadership lens): commitments on data responsibility were not operationalised - one platform concentrated agent identities, national civil records and criminal investigation data on a path reachable from one weakly authenticated app, so the exposure extended from payroll-like records to informant-sensitive investigation data (causal role: Amplifying). RM22 (Strategy to Leadership lens): no authentication model proportionate to the data risk was required or prioritised for the police app and its accounts - token-less requests and unchanged device-bound logins reported as working until after the leak, with leadership's only visible response being shutdown rather than an authentication programme (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

The intrusion mechanism (token-less app API, spoofable IMEI+PIN logins, path to Imperium) rests on FocaLeaks' own claims as reported by DataBreaches.net - unverified, and PNC never confirmed the hack beyond speaking of an investigation; the classification deliberately does not rest on those claims. The ddosecrets.com link in the case file is a leak-data archive and was not opened, per the research boundaries; DDoSecrets' findings are used only as reported by DataBreaches.net. The CoinDesk article (Mario Gómez arrest/release, 1 Sep 2021, no charges) substantiates the motive stated in the row description. Data-quality: the case file's data_theft field scores the theft as 'non-sensitive information (1 point)', while the reporting ties the published agent data to filed complaints about danger to life - the intensity label understates what was exposed. Director Arriaza Chicas' characterisation of an 'old database' is contradicted within the same reporting by DataBreaches.net's finding that dumped agent records were current at the date of the Gomez arrest; no official forensic finding, regulator decision or later prosecution was found in later reporting. The attribution_source_url in the case file (databreaches.net claim article) has been opened and cited; web.archive.org not needed as all cited pages opened. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: coindesk.com was unreachable at check time (timeout); the page was opened and read during research.