In what stands as one of the most extensive national identification breaches in European history, the Danish government has confirmed that unauthorized perpetrators accessed the Central Person Register (CPR), extracting names, addresses, and 10-digit CPR identification numbers belonging to approximately 8.8 million individuals. The incident was not caused by a direct infrastructure compromise of the registry itself, but rather by the systematic abuse of authorized API credentials hijacked from a private commercial partner permitted to interface with the national database.
Breach Anatomy: Supply Chain Abuse of Trusted Government Integrations
The Danish CPR system serves as the foundational civic identity backbone of Denmark. Every resident is assigned a unique, immutable 10-digit CPR number used for banking, health services, taxation, property leasing, and digital authentication (MitID).
To facilitate identity verification and address verification, select vetted commercial enterprises (such as financial institutions, credit bureaus, and utility providers) are granted direct query access to the CPR database via automated API endpoints.
According to preliminary forensic findings from the Agency for Digital Government (Digitaliseringsstyrelsen), the attackers acquired valid administrative API service credentials from an authorized private Danish enterprise, executing distributed batch lookups to circumvent basic threshold rate limits.
Exfiltrated Data Elements & Threat Exposure Matrix
| Exfiltrated Data Element | Volume & Sensitivity | Primary Exploitation Vectors | Mitigation / Countermeasure |
|---|---|---|---|
| Full Legal Name | 8.8 Million Records (Public/Low) | Spear-phishing correlation and identity matching | DMARC enforcement and anti-phishing training |
| Residential Address | 8.8 Million Records (Medium) | Physical mail fraud, social engineering, stalking | Enforce official address protection flags |
| 10-digit CPR Number | 8.8 Million Records (Critical National ID) | Bank account verification bypass, SIM swaps, credit fraud | Step-up MitID 2FA verification for credit checks |
Step-by-Step Incident Response & Partner API Containment Playbook
API platform operators and government identity authorities must execute concrete containment steps:
- Immediate Revocation of Compromised Mutual TLS (mTLS) Certificates:
# Revoke compromised partner certificate serial number in OpenSSL CA database openssl ca -revoke /etc/pki/CA/certs/compromised_partner.crt -crl_reason keyCompromise # Generate updated Certificate Revocation List (CRL) openssl ca -gencrl -out /etc/pki/CA/crl/partner_api.crl # Reload API Gateway (NGINX/Envoy) to apply updated CRL sudo nginx -s reload - Audit API Access Logs for Batch Enumeration Patterns:
# Query NGINX API logs for high-frequency CPR query requests from partner IP blocks awk '{print $1, $4, $7, $9}' /var/log/nginx/cpr_api_access.log | grep "/api/v2/citizens/lookup" | cut -d: -f1-2 | sort | uniq -c | sort -nr | head -n 20 - Enforce Strict Behavioral Rate Limiting and CIDR Restrictions:
# NGINX Configuration to enforce IP whitelisting and rate limits geo $allowed_partner_net { default 0; 195.128.45.0/24 1; # Authorized corporate proxy CIDR } limit_req_zone $binary_remote_addr zone=cpr_lookup_limit:10m rate=5r/s; server { location /api/v2/citizens/ { if ($allowed_partner_net = 0) { return 403; } limit_req zone=cpr_lookup_limit burst=10 nodelay; proxy_pass https://cpr-backend-cluster; } }
National Defense & Policy Recommendations
Authorities clarified that individuals enrolled in official name and address protection programs (navne- og adressebeskyttelse) were shielded by database-level access filters. Going forward, Denmark has initiated mandatory behavioral anomaly detection across all sovereign API query consumers.



