Denmark population register breach exposes 8.8 million records via abused third-party access
Danish authorities confirmed on October 5, 2026 that unauthorized people misused a private company’s legitimate access to Denmark’s Central Person Register, known as the CPR, and obtained names, addresses, and CPR numbers for about 8.8 million registered people. The register holds about 11 million records in total, including people who are deceased and people who have moved abroad. Records with protected names and addresses were excluded, according to the CPR Administration.
The company was Pays ApS, a two employee IT firm based in Odense. Its managing director confirmed on October 9 that the firm’s lawful access to search the register had been abused. Pays had authorized access to validate business customers’ records. Documents obtained by broadcaster TV 2 say the attacker gained access on September 10, 2026, and ran about 14 million automated searches through September 20, 2026. The activity was detected on October 2, when a staffer noticed an invoice showing unusually high activity from Pays, and the access was then cut off.
Danish newspaper Politiken reported that a person claiming responsibility said at least three Pays accounts, including an administrator account, used the password 123456. That password claim is reported, not confirmed by Danish authorities, and the person also claimed to have no intention of selling or leaking the data. Whether or not the password detail is confirmed, the confirmed facts are enough: valid third party credentials, no effective anomaly alerting, and nearly three weeks from first access to detection.
What to do
- Audit every third party account that can reach your systems or your data. Enforce unique strong passwords and multi factor authentication, and remove accounts belonging to former employees or ended contracts.
- Alert on anomalous usage volume from any single account, not only on failed logins. Fourteen million lookups from a two person firm should have triggered an alert long before the monthly invoice.
- Make sure you can revoke third party access immediately, and review vendor access on a schedule instead of assuming it is still needed.
This breach did not start with a software flaw. It started with trusted access that was never rechecked. ZeroBreach audits inventory the third party connections, integrations, and forgotten accounts on your stack, so trusted access gets reviewed before it becomes the breach.